FS#14096 - extra/gnome-terminal 2.26.0-1 fails to execute

Attached to Project: Arch Linux
Opened by hyperb0lix (hyperb0lix) - Saturday, 04 April 2009, 21:42 GMT
Last edited by Jan de Groot (JGC) - Friday, 29 May 2009, 17:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

extra/gnome-terminal 2.26.0-1 fails to execute. The relevant error message is `Failed to contact the GConf daemon; exiting.' I have reinstalled both the gconf and gnome-terminal packages, yet the error persists. I suppose this is a problem with the new gconf update.

Additional info:

* package version(s)
extra/gconf 2.26.0-2 and/or
extra/gnome-terminal 2.26.0-1

* config and/or log files etc.

[~] gnome-terminal
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Failed to contact the GConf daemon; exiting.

Steps to reproduce:

Run gnome-terminal after the latest gconf update.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 29 May 2009, 17:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in 2.26.2-2.
Comment by Jan de Groot (JGC) - Saturday, 04 April 2009, 21:54 GMT
Did you try rebooting or killing all gnome-related processes after updating? Also remember that the dbus session bus is a requirement these days. Not having this means total failure on modern desktop environments.
Comment by hyperb0lix (hyperb0lix) - Saturday, 04 April 2009, 21:57 GMT
Yeah, I tried reinstalling both packages and rebooting. I have dbus, and gnome-terminal is my only GNOME app.
Comment by Cameron (starfreakclone) - Saturday, 04 April 2009, 22:00 GMT
Confirmed:
[~>] gnome-terminal
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Failed to contact the GConf daemon; exiting.

Package Info:
[~>] pacman -Qi gnome-terminal
Name : gnome-terminal
Version : 2.26.0-1
URL : http://www.gnome.org
Licenses : GPL
Groups : gnome-extra
Provides : None
Depends On : gconf>=2.26.0-2 vte>=0.20.0 startup-notification>=0.9
Optional Deps : None
Required By : None
Conflicts With : None
Replaces : None
Installed Size : 8496.00 K
Packager : Jan de Groot <jgc@archlinux.org>
Architecture : i686
Build Date : Sun 29 Mar 2009 06:29:50 AM MDT
Install Date : Sat 04 Apr 2009 03:11:29 PM MDT
Install Reason : Explicitly installed
Install Script : Yes
Description : The GNOME Terminal Emulator
Comment by Jan de Groot (JGC) - Saturday, 04 April 2009, 22:06 GMT
As said, you need the dbus session bus running. Having dbus installed is not enough. How do you start your desktop environment?
Comment by hyperb0lix (hyperb0lix) - Saturday, 04 April 2009, 22:13 GMT
I have dbus installed, and it _is_ running. Also, I don't use a desktop environment. Perhaps I should have been clear. Here's the relevant evidence:

[~] /etc/rc.d/dbus start
:: Starting D-BUS system messagebus [BUSY]
Failed to start message bus: The pid file "/var/run/dbus.pid" exists, if the message bus is not running, remove this file
[FAIL]
[~] pgrep dbus
6533 /usr/bin/dbus-daemon --system
7051 dbus-launch --autolaunch d1380c0fa7436bd4f33bf6ea49199a52 --binary-syntax --close-stderr
7052 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
10876 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
10886 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
10896 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
10901 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
Comment by Jan de Groot (JGC) - Saturday, 04 April 2009, 22:18 GMT
I wonder why you have the insane amount of 5 dbus session daemons running. Launch your window manager or whatever you're using from .xinitrc using dbus-launch --exit-with-session and you should be fine.
Comment by hyperb0lix (hyperb0lix) - Saturday, 04 April 2009, 22:40 GMT
I too wonder why I have the insane number of five dbus session daemons running. I suppose it's because I didn't start Fluxbox through dbus-launch, so each dbus-using app I had required an instance of dbus-daemon. Other than cluttering up my ps, it hasn't been a problem until now. I simply followed the wiki, Jan, and there was nothing about starting Fluxbox through dbus-launch (it makes sense to do so, though). Your fix worked:

[~] fgrep fluxbox .xinitrc
exec dbus-launch --exit-with-session startfluxbox
[~] pgrep dbus
6605 /usr/bin/dbus-daemon --system
7095 dbus-launch --exit-with-session startfluxbox
7096 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
[~] gnome-terminal
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
^C
[~]

Thanks. :)
Comment by Angel Velasquez (angvp) - Friday, 15 May 2009, 08:40 GMT
  • Field changed: Percent Complete (100% → 0%)
Works for you doesn't mean it's solved ..

http://bbs.archlinux.org/viewtopic.php?id=69153

See this thread, in the fist page the user giorgidze found a solution.

Cheers
Comment by Jan de Groot (JGC) - Friday, 15 May 2009, 08:46 GMT
This works as long as you have a dbus session bus that works. As for a not-working dbus session bus due to things like gksu: then it's a duplicate of  bug 11906 .
Comment by Angel Velasquez (angvp) - Friday, 15 May 2009, 15:06 GMT
I do have a working dbus session ..
Comment by Jan de Groot (JGC) - Friday, 15 May 2009, 15:21 GMT
So what error messages do you get when launching gnome-terminal?
Comment by Jan de Groot (JGC) - Sunday, 17 May 2009, 14:22 GMT
It appears that gconf_ping_daemon() returns false when gconf is not running. It doesn't do an attempt to start it either. This means that gnome-terminal won't execute until a running gconf daemon is present. I'll have a look at removing this call, as this is clearly not wanted behaviour.

Loading...