Skip Menu |

This queue is for tickets about the Tk CPAN distribution.

Report information
The Basics
Id: 127708
Status: rejected
Priority: 0/
Queue: Tk

People
Owner: Nobody in particular
Requestors: duncan_j_ferguson [...] yahoo.co.uk
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 804.034
Fixed in: (no value)



Subject: Tk::Dialog bug: bad pad value "3m": must be positive screen distance
$ ./tk_bug bad pad value "3m": must be positive screen distance at /usr/lib64/perl5/vendor_perl/Tk/Widget.pm line 1218. at /usr/lib64/perl5/vendor_perl/Tk/Widget.pm line 203. This issue is not seen when converting to using Tk::DialogBox This bug is seen on Fedora Core 29 using Tk version 804.034 This bug is not seen on Debian Jessie using Tk 804.033 Minimal example code attached.
Subject: tk_bug
Download tk_bug
application/octet-stream 220b

Message body not shown because it is not plain text.

On 2018-11-18 04:17:45, duncs wrote: Show quoted text
> $ ./tk_bug > bad pad value "3m": must be positive screen distance at > /usr/lib64/perl5/vendor_perl/Tk/Widget.pm line 1218. > at /usr/lib64/perl5/vendor_perl/Tk/Widget.pm line 203. > > This issue is not seen when converting to using Tk::DialogBox > > This bug is seen on Fedora Core 29 using Tk version 804.034 > This bug is not seen on Debian Jessie using Tk 804.033 > > Minimal example code attached.
I cannot reproduce it. What I tried is: - running your script on a Debian/jessie system with different perl + Tk versions - running your script on a Fedora 28 VM with the system perl and a self-compiled perl, both using Tk 804.034 - use the Dockerfile below. Save these lines as "Dockerfile", add the test script into the same directory, add also something like $window->after(10*1000, sub { $window->destroy }); before the MainLoop so the test script terminates after 10s, and run: docker build -t perl-test -f Dockerfile . && docker run perl-test FROM fedora:29 RUN yum -y install perl-Tk RUN yum -y install xorg-x11-server-Xvfb ADD tk_bug /tmp/tk_bug RUN Xvfb :123 & sleep 10; echo "Start test script"; DISPLAY=:123 perl /tmp/tk_bug So maybe something else is different in your system. Maybe an issue with present or nonexisting fonts? Unlikely. Maybe stray X resource definitions? Possible, so I was not able to reproduce a problem using something like perl tk_add -xrm "*pad: 3m" An idea would be to check the output of "xrdb -query" for suspicious definitions. Regards, Slaven
On Sat Feb 02 05:27:31 2019, SREZIC wrote: Show quoted text
> Possible, so I was not able to reproduce a problem using > something like > > perl tk_add -xrm "*pad: 3m" > > An idea would be to check the output of "xrdb -query" for suspicious > definitions.
The output from that command all looks okay to me: $ xrdb -query Xft.dpi: 96 Xft.antialias: 1 Xft.hinting: 1 Xft.hintstyle: hintslight Xft.rgba: none Xcursor.size: 24 Xcursor.theme: Adwaita I have updated to the latest version of FC29 tonight and retest the bug; now cannot reproduce it, so I think this must be an issue in FC29 that is now (hopefully) fixed by them Il mark this ticket as closed - thanks for looking into it. Duncs