On Thu, Oct 14, 2010 at 8:07 PM, James Westby <email address hidden> wrote: > Do you still have the environment around to test with?
Yep.
> Is there a dbus session bus running when you get that failure?
It would seem so:
benji@kubuntu:~$ ps aux | grep dbus | cut -c66- dbus-daemon --system --fork dbus-launch --autolaunch 5375d1ed127ac5597be0225d4caf691b --binary-syntax --close-stderr /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager /usr/bin/dbus-launch --exit-with-session x-session-manager /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session grep --color=auto dbus -- Benji York
On Thu, Oct 14, 2010 at 8:07 PM, James Westby <email address hidden> wrote:
> Do you still have the environment around to test with?
Yep.
> Is there a dbus session bus running when you get that failure?
It would seem so:
benji@kubuntu:~$ ps aux | grep dbus | cut -c66- 97be0225d4caf69 1b dbus-launch --exit-with-session x-session-manager dbus-launch --exit-with-session x-session-manager
dbus-daemon --system --fork
dbus-launch --autolaunch 5375d1ed127ac55
--binary-syntax --close-stderr
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
/usr/bin/ssh-agent /usr/bin/
/usr/bin/
/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
grep --color=auto dbus
--
Benji York