GNOME Bugzilla – Bug 106489
font-properties dialog won't start on /desktop/gnome/font_rendering/dpi=0
Last modified: 2004-12-22 21:47:04 UTC
Package: control-center Severity: normal Version: debian 2.2.0.1-1 Synopsis: font-properties dialog crashes on /desktop/gnome/font_rendering/dpi=0 Bugzilla-Product: control-center Bugzilla-Component: other capplets Description: Description of Problem: While trying to get font-properties to use the DPI as reported by X (instead of having to manually specify it (it was wrong)), I managed to crash gnome-font-properties. Steps to reproduce the problem: 1. set gconf key /desktop/gnome/font_rendering/dpi to empty string 2. gconf-editor replaces empty string with 0 3. attempt to start font-properties through Applications -> Desktop Preferences -> Font Actual Results: No font properties window appears. This appears in .xsession-errors: The program 'gnome-font-properties' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 377 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Expected Results: See the font-properties window I note that the "Advanced Font Properties" DPI widget replaces a value <50 with 50. Presumably the same thing should happen when reading the gconf value too. How often does this happen? every time dpi is set to 0 Additional Information: (man its hard work to report bugs in gnome. i was forced to create a bugzilla login and wait for a password email before i could even report a bug?? jdub mentioned that i could use bug-buddy without having a bugzilla account, but even bug-buddy requires you to know that "that popup window there" is actually control-center/font-properties, and then you have to find a version.. surely you can do a simple "click on window, get WM_COMMAND property (i note gnome doesn't set this) or something, grab --version output, email bug description with info and maybe screenshot") ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-18 21:31 ------- Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Hmmm, works for me.
I've added some sanity checking to cath dpi < 50 from goncf