The original Leopard X11 did not have this problem. I don't have a Leopard with the version just prior to X11-2.1.1 at this point in time to determine if it was X11-2.1.1 where the problem occurred or not (I can probably get there by the end of the weekend). Merle On Dec 15, 2007, at 8:38 PM, Merle Reinhart wrote:
I've been doing a bit more testing with X11-2.1.1 and find that the autolaunching stuff doesn't work if one user already has the Xserver started. At that point, any other user logging in via fast-user switching is not able to then use X11 (attempting to set DISPLAY to : 1.0 and manually start X11.app winds up in an infinite loop with Xquartz still trying to talk to the server at :0.0 which is owned by the other user).
At this point in time, I have not been about to find a workaround that would allow more than one user to utilize X11.app at the same time. Could this be because launchd is explicitly hard-coded to look at the :0 socket when the socket should increase based upon the number of logged in users?
This is potentially a problem with multi-user systems where X11 may be needed.
Merle
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev