On 9/24/07, Sebastian Dröge <[EMAIL PROTECTED]> wrote: > > Hi, > your two bugs (gnome-session and control-center) might probably be > related. Is dbus-daemon running in your session? What's the output of > ps aux | grep dbus > dbus-daemon is definitely running.
103 3167 0.0 0.2 2900 1224 ? Ss Sep23 0:00 /usr/bin/dbus-daemon --system root 3179 0.0 0.2 2768 1252 ? S Sep23 0:00 dbus-daemon --session --print-address --nofork ian 13968 0.0 0.1 2100 664 pts/0 S+ 18:55 0:00 grep dbus ian 24138 0.0 0.0 2896 448 ? S 09:31 0:00 dbus-launch --autolaunch 787540454d1d29f3e144ea38b2d22d00 --binary-syntax --close-stderr ian 24139 0.0 0.1 2768 1012 ? Ss 09:31 0:01 dbus-daemon --fork --print-address 25 --print-pid 27 --session ian 24140 0.0 0.1 2768 872 ? Ss 09:31 0:00 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 8 --session > Does for example "notify-send blabla" (install libnotify-bin) work? This > will use the dbus session daemon. > Yes this works just fine. > > ... > > "Yelp-ERROR **: 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. > > > > aborting... > > Aborted" > > ... This is not the main error. I think the main error is that it cannot find the help file?? I'll double check whether dbus is running when the gsd error occurs. It is running at present when I get the help problem. If I don't reply then dbus-daemon is running for the other issue as well. Ian
