After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 398568 - gnome-font-properties crashes when run in an x11vnc session
gnome-font-properties crashes when run in an x11vnc session
Status: RESOLVED DUPLICATE of bug 378338
Product: gnome-control-center
Classification: Core
Component: [obsolete] font properties
git master
Other Linux
: Normal major
: ---
Assigned To: Federico Mena Quintero
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-19 23:42 UTC by Josselin Mouette
Modified: 2007-01-31 17:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Josselin Mouette 2007-01-19 23:42:55 UTC
[ forwarded from http://bugs.debian.org/407470 ]

It seems that in when run in x11vnc, GTK is unable to get the physical screen dimensions, and returns 0. However the font properties dialog uses them to extract the DPI value.

The following gdb session explains all:

0x0804e645 in cb_show_details (button=0x807b5f0, parent=0x80c2010)
    at /home/chris/src/gnome-control-center/control-center-2.14.2/./capplets/font/main.c:856
856                     dpi = floor ((gdk_screen_width () / gdk_screen_width_mm () +
(gdb) print gdk_screen_height()
$1 = 864
(gdb) print gdk_screen_height_mm()
$2 = 0
(gdb) print gdk_screen_width()
$3 = 1152
(gdb) print gdk_screen_width_mm()
$4 = 0
(gdb) where
  • #0 cb_show_details
    at /home/chris/src/gnome-control-center/control-center-2.14.2/./capplets/font/main.c line 856
  • #1 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0

Apparently, the bug is still present in HEAD. This could be fixed by adding a check that these values are non-zero.
Comment 1 Federico Mena Quintero 2007-01-31 17:27:10 UTC
I'll take care of this along with bug #378338, which is in general about sanitizing the X server's DPI values when they are bogus.
Comment 2 Federico Mena Quintero 2007-01-31 17:31:11 UTC

*** This bug has been marked as a duplicate of 378338 ***