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 590774 - libgnome required to get the default monospace font
libgnome required to get the default monospace font
Product: gnome-terminal
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Reported: 2009-08-04 19:41 UTC by Emilio Pozuelo Monfort
Modified: 2011-02-03 22:12 UTC
See Also:
GNOME target: 3.0
GNOME version: 2.27/2.28

Description Emilio Pozuelo Monfort 2009-08-04 19:41:59 UTC
[ Initially reported on ]


The libgnome dependency was removed in 2.26. However it's still needed to get the default monospace from GConf, as /desktop/gnome/interface/monospace_font_name (read in terminal-app.c) is shipped in libgnome.

Without libgnome installed, gnome-terminal doesn't start:

  ERROR:terminal-app.c:1433:terminal_app_init: assertion failed:
  (app->system_font_desc != NULL)

Can this be fixed so that gnome-terminal works without libgnome?
Comment 1 Christian Persch 2009-08-04 19:52:24 UTC
Maybe the shemas should be moved to a non-deprecated package then, maybe gnome-desktop or gnome-settings-daemon or gnome-control-centre ?
Comment 2 Emilio Pozuelo Monfort 2009-08-04 21:19:40 UTC
I've sent a mail to d-d-l asking for opinions.
Comment 3 Christian Persch 2009-08-13 12:46:25 UTC
I don't see how that crash in comment 0 can happen, EXCEPT if you use the debian or ubuntu package of gnome-terminal that has the bogus gconf patch applied. The g-t code uses "Monospace 10" as default font when the schema can't be found.
Comment 4 Emilio Pozuelo Monfort 2009-08-13 23:02:20 UTC
Do you mean what comment 5 in bug 564649 suggests? Seriously that's causing this crash?
Comment 5 Christian Persch 2009-08-13 23:20:57 UTC
I mean the patch in . If you're using debian's g-t, then yes, it very likely causes this crash, since it brings g-t into an unexpected situation (hence the assertion failure).

Moving the schemas to a non-deprecated module has independent value, of course, and is a valid bug.
Comment 6 Jan de Groot 2009-11-14 23:48:35 UTC
This also happens with an unpatched gnome-terminal when the libgnome gconf schemas are unregistered, so it's not a debian-specific problem.

When the libgnome schemas aren't installed in the gconf registry, there will be no key for the default font. When there's no key for the font, there won't be any call to terminal_app_system_font_notify_cb, which means the fallback font isn't set either. I started gnome-terminal from gdb using a breakpoint on this function, the breakpoint is never reached.
Comment 8 Christian Persch 2010-04-13 13:46:16 UTC
The patch is wrong.

This will be fixed when porting Gnome to gsettings, no need for any work until then.
Comment 9 Christian Persch 2011-02-03 22:12:33 UTC
Since the full gsettings port will have to wait for at least 3.1, I just ported the monospace font setting to gsettings for now.