[In a message on Tue, 29 Mar 2005 16:47:23 +0100, "James Weatherall" wrote:] >Damjam, > >As previously stated, this is a bug in Gnome that prevents multiple Gnome >sessions to co-exist on the same machine for the same user.
If I recall correctly, it's a little worse than that. The Gnome people are convinced no one has an NFS-shared home directory, so corporate users can't run multiple gnome sessions on multiple machines if they share their home directory. Actually, I shouldn't say that they don't expect one to have an NFS-mounted home directory, as that's been discussed in their forums. Rather, they don't expect one to log in (graphically) to more than one machine at a time. So the lock in ~/.gconfd/lock isn't tied to a particular host. This is probably more of an architectural decision, since I'm sure that there is a LOT of writing done to the gconfd files, and you wouldn't want to sessions stomping on each other. So it's just bad design. You *COULD* change $HOME and then run gnome-session, and it would probably work, but break almost everything else (you could reset $HOME to the right place in all your subshells). Sean _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
