https://bugzilla.suse.com/show_bug.cgi?id=1137203 https://bugzilla.suse.com/show_bug.cgi?id=1137203#c29 --- Comment #29 from Reinhard Max <max@suse.com> --- I finally got to reproduce it after changing the graphics device from virtio-gpu-pci to qxl-vga in runqemu.nokvm. The problem is that in this case the X server reports a zero sized screen and consequently a practically infinite screen resolution which can be seen in the output of xdpyinfo: --- snip --- screen #0: dimensions: 1024x768 pixels (0x0 millimeters) resolution: 2147483647x2147483647 dots per inch --- snap --- Tk uses this information to initialize the scaling factor for translating between points and pixels which in turn is used for rendering fonts if their size is specified in points. This value can be queried by interactively running the "tk scaling" command in wish, and it can be changed by adding a value, e.g. "tk scaling 1.25". In X sessions having the absurd screen size values shown above, "tk scaling" gets initialized as infinity (Inf), resulting in the font's pixel size to be divided down to zero and hence the text isn't visible. As this test is meant to test if Tk works rather than looking for bugs in the underlaying X server, I suggest to set the scaling factor to a useful value (e.g. 1.0) at the beginning of the script, bevore creating any widgets. To check if the X server reports a reasonable screen size and resolution, a separate test could be added that parses the output of xdpyinfo and fails if the values don't look useful. Not sure who would be the right assignee for this bug at this point, but it is definitely not a bug in Tk. -- You are receiving this mail because: You are on the CC list for the bug.