Sjoerd Simons schrieb: > On Sat, Sep 16, 2006 at 01:38:41AM +0200, André Wendt wrote: >> Hi Sjoerd, >> >>> That doesn't help, you start a session bus but the environment >>> variables won't be set. If the process in $DBUS_SESSION_BUS_PID could >>> you check if running ``dbus-deamon --session'' gives some usefull >>> error message? >> ``dbus-deamon --session'' gives no error message whatsoever. If I invoke >> that command, none of the variables are set although the process is >> active until it receives SIGINT. >> >> Before that, there is a session already running, ps aux tells me it was >> invoked using ``dbus-daemon --fork --print-pid 8 --print-address 6 >> --session'', but that one obviously doesn't set the variables either. > > dbus-launch is what should set the environment variables, not dbus-daemon > itself. I let you run dbus-daemon to see if something bad happend to it on > your > system. > > According to your original mail the DBUS_SESSION_BUS_ADDRESS is set (Could you > recheck that?) so there shouldn't be a problem connecting to your session > bus...
I re-checked, DBUS_SESSION_BUS_ADDRESS is *not* set (echo prints nothing). I guess this was a misunderstanding, sorry about that. What I did was run ``dbus-launch'' as, according to the manpage With no arguments, dbus-launch will simply print the values of DBUS_SESSION_BUS_ADDRESS and DBUS_SESSION_BUS_PID. This is why I said the two variables are set, but they aren't. > Also please try to re-login if you didn't in the mean time. Maybe the running > session bus is too old.. Not really, I logged in a couple of times since the initial report. > If that doesn't help please send me the output of strace dbus-monitor.. I don't have an executable named dbus-monitor on my system. Please note I'm not running the unstable version but testing's 0.62-4... Regards, André
