GNOME Bugzilla – Bug 576346
gksudo gnome-terminal fails with "Failed to contact the GConf daemon"
Last modified: 2009-04-15 14:27:41 UTC
Please describe the problem: With gconf2 2.26.0, i am unable to start gnome-terminal, other applications work fine. Steps to reproduce: 1. open terminal 2. type gksu -d -S gnome-terminal Actual results: andreas@andreas-desktop:~$ gksu -d -S gnome-terminal No ask_pass set, using default! xauth: /tmp/libgksu-3SHlAA/.Xauthority STARTUP_ID: gksu/gnome-terminal/17703-0-andreas-desktop_TIME19032252 cmd[0]: /usr/bin/sudo cmd[1]: -H cmd[2]: -S cmd[3]: -p cmd[4]: GNOME_SUDO_PASS cmd[5]: -u cmd[6]: root cmd[7]: -- cmd[8]: gnome-terminal buffer: -Failed to contact the GConf daemon; exiting.- brute force GNOME_SUDO_PASS ended... No password prompt found; we'll assume we don't need a password. Failed to contact the GConf daemon; exiting.xauth: /tmp/libgksu-3SHlAA/.Xauthority xauth_env: /home/andreas/.Xauthority dir: /tmp/libgksu-3SHlAA Expected results: A root-terminal would open. Does this happen every time? Yes Other information: Possibly related/a dupe of bug #555745 Reported on Launchpad: https://bugs.launchpad.net/bugs/328575
Dup of bug 555745 indeed; see also gnome-terminal bug 561663. *** This bug has been marked as a duplicate of 555745 ***
It isn't a duplicate of 555745. All application work fine when launched with sudo or with ssh -Yf, only gnome-terminal fails with "Failed to contact the GConf daemon; exiting." Please remove the duplicate mark