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 570588 - gnome-terminal exits if gconf is not running
gnome-terminal exits if gconf is not running
Status: RESOLVED DUPLICATE of bug 564649
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-05 05:35 UTC by Matthias Clasen
Modified: 2009-02-05 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2009-02-05 05:35:10 UTC 
First reported here: https://bugzilla.redhat.com/show_bug.cgi?id=484134

When connected from a remote with X forwarded via ssh after typing
'gnome-terminal' I am seeing the following:

Xlib:  extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib:  extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib:  extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib:  extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib:  extension "Generic Event Extension" missing on display "localhost:11.0".
Failed to contact the GConf daemon; exiting.

and gnome-terminal fails to start.



I understand that gnome-terminal dying due to not having sane defaults is a problem, but simply exiting in the absence of gconfd is a knee-jerk and wrong way to handle that problem. Instead, fix gnome-terminal to have sane defaults to fall back to in the absence of gconf.
Comment 1 Christian Persch 2009-02-05 12:57:50 UTC 
It was just crashing in this case before, so I added the graceful non-crash exit in bug 561663. Bug 564649 deals with making g-t work without gconf. 

Note that the root cause of this is that gconf is now using dbus and there's no bus available when remoting; see e.g. bug 555745 and https://bugs.freedesktop.org/show_bug.cgi?id=17970 .

*** This bug has been marked as a duplicate of 564649 ***
Comment 2 Matthias Clasen 2009-02-05 14:58:26 UTC 
Regardless of that, its not ok to refuse to work if gconf is not running...