Thanks Patrick!
That explains it perfectly.
I didn't know that DBUS needed X for setup.
On Wed, 2010-05-26 at 10:14 +0200, Patrick Ohly wrote:
On Sat, 2010-05-22 at 20:34 +0100, Jeff wrote:
> This does not work, I thought I was just forwarding X and so DBUS
> communications for evolution should not be effected...apparently it's
> more complex than that though...
D-Bus depends on X for some of its operations, in particular
boot-strapping the D-Bus session. If you ssh into a machine, you end up
with your own private D-Bus session and private evolution-data-server
daemon. If you have another D-Bus session active accessing the same home
directory, this is probably leading to race conditions
regarding .evolution file access and all kinds of nasty problems.
If you need to do something like this, then better ensure that all your
processes in the machine you log into run inside the session started by
ssh.