Yeah, this is a well-known race condition between xinitrc (which starts the window manager) and the first client being started. It was present in earlier releases as well, but the startup code path was optimized in 2.3.0 (and further in 2.3.1), so now the launchd socket is actually "winning"... I'm a few steps away from having this solved for good, but for now, I'm still using a sleep() to delay opening the first X11 connection from the launchd socket. --Jeremy On Aug 16, 2008, at 10:28, Adam Mercer wrote:
On Sat, Aug 16, 2008 at 11:40 AM, Jeremy Huddleston <jeremyhu@apple.com
wrote: so please test it out and let me know if there's anything serious with it (regressions over 2.2.3 or 2.3.0 being or primary concern).
One thing I've recently noticed with the 2.3.x series so far is that if you start an xterm from Terminal.app (without X11.app running), a white box appears in the top left hand corner and then a few seconds later the window border and title bar is displayed. All subsequent xterms, or if X11.app is already running, start up with the border and window title. So far I've only noticed this with small applications like xterm or xclock. Its a minor issue but this wasn't present in version prior to 2.3.0.
Cheers
Adam _______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev