It's odd that I'm seeing this, yet I see no mention of anyone else
having
the same issue.
If I start an xterm in Terminal.app, X11 will start as expected, but
oddly,
the xterm will not display until I quit X11.app (by clicking it on
the Dock,
then using cmd-q) and it restarts. Once this restart has taken
place, the
xterm will open, and other X apps will be able to use the display.
I've had a couple of reports of this -- sometimes it causes X11 to
start chewing up 100% of the CPU time, sometimes it seems to just
hang. Sometimes it works, too! Really!
Feel free to file a bug report. I'm looking into it, but can't say
what's causing it -- maybe some sort of race condition?
The fix is then to either quit X11, and have it restart while trying
to
start an xterm, or to delete .Xauthority and start over. Now, also
oddly,
sometimes I get this:
$ xterm
X connection to /tmp/launch-YkJO02/:0 broken (explicit kill or server
shutdown).
This message is harmless -- it's just xterm informing you that the
reason it died was that you killed the X server.
--
Ben Byer
CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
