Launching application which need another window fails from shell

SkyerSK · 02-12-2011, 10:16 AM

Hello,
I hope I wrote correct title to this thread, since I am not sure where does this problem comes from, or what causes it.

When I try to launch application which runs in another window (not inside shell), it always fails with this kind of message: (example from gnome-terminal)

Code:

** (gnome-terminal:2477): WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported

Failed to get the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Falling back to non-factory mode.
Failed to summon the GConf demon; exiting.  Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

I am running it as root, have GNOME installed and running, and also fresh install of gconf.

Could you please help me or guide me to correct answer/solution for this problem? I heard this was considered as bug in past, but I haven't found good solution or am not that good using google.

Thanks much for any help.

MTK358 · 02-12-2011, 10:24 AM

Do non-GNOME applications work (such as xterm)?

SkyerSK · 02-12-2011, 10:38 AM

Yes, without any problems or warning messages.

MTK358 · 02-12-2011, 12:01 PM

What distro are you using?

Do you have D-Bus installed and running in the background?

SkyerSK · 02-13-2011, 03:10 AM

Debian Sqeeze, on amd64 architecture. Environment (Gnome) is installed from original iso image, downloaded from debian.org.

MTK358 · 02-13-2011, 08:11 AM

Do you have D-Bus installed and is it running as a daemon?

SkyerSK · 02-13-2011, 11:05 AM

Thanks for your answer, I am quite novice when it comes to Gnome (and maybe Linux at all), but as D-Bus should be installed and running as daemon. So from ps aux, there is dbus-daemon runnig twice, and dbus-launch once. Here is exact output:

Code:

root@computer:/# ps aux|grep dbus
101       1367  0.0  0.0  23672  1396 ?        Ss   16:12   0:00 /usr/bin/dbus-daemon --system
skyer     1806  0.0  0.0  11876   428 ?        Ss   16:13   0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager
skyer     1809  0.0  0.0  26104   780 ?        S    16:13   0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
skyer     1810  0.0  0.0  23652  1304 ?        Ss   16:13   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root      2399  0.0  0.0   7548   836 pts/0    S+   17:59   0:00 grep dbus

Note: I don't have any user called 101 in my system. I suspect it to be some kind of name resolution fail - from /etc/passwd:
"messagebus:x:101:103::/var/run/dbus:/bin/false. Thanks for help.

MTK358 · 02-13-2011, 11:07 AM

I might not be able to help further since I'm not very familiar with the inner workings of desktop environments, it's just that many DEs have components that need to communicate with D-Bus or will otherwise fail.

SkyerSK · 02-13-2011, 11:21 AM

Thanks for reply,
this problem occurs only when running as root. I don't know much about graphical environments neither, so this is kinda mysterious for me.

(Edited.)