Actually, I take that back. The connection to :0.0 is NOT the xterm. It's xinit and it's expected. ... I'm puzzled about those AUDIT lines though... --Jeremy On Jun 15, 2008, at 10:23, Jeremy Huddleston wrote:
15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 2 rejected from local host (uid 501) 15/06/08 18:12:33 org.x.startx[90998] AUDIT: Sun Jun 15 18:12:33 2008: 91062 X: client 1 rejected from IP fe80::1 15/06/08 18:12:33 org.x.startx[90998] Xlib: connection to ":0.0" refused by server 15/06/08 18:12:33 org.x.startx[90998] Xlib: No protocol specified 15/06/08 18:12:33 org.x.startx[90998] waiting for X server to begin accepting connections
So this is the heart of the problem. It looks like for some reason, you're connecting to DISPLAY=:0.0 and not DISPLAY=/tmp/launchd-XXXX/:0
Any idea why that may be? The fact that X11 is being triggered to start implies that you have DISPLAY=/tmp/launchd-XXXXX/:0 ... but the log clearly shows that Xlib was being told to connect to :0 ...
The fact that the connection was denied is... well... expected because you're connecting to it before the server is accepting connections (hence the message from xinit at the bottom there that it's waiting for the server to accept connections before it runs the xinitrc.
--Jeremy _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev