Re: X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
Re: X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
- Subject: Re: X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
- From: "stephen joseph butler" <email@hidden>
- Date: Sun, 16 Mar 2008 23:58:29 -0500
On Sun, Mar 16, 2008 at 11:29 PM, Tom Lane <
email@hidden> wrote:
Since updating to 2.1.4, I've noticed that sometimes a program trying
to connect to DISPLAY=":0.0" will work, and sometimes it won't. I see
that X11 now preferentially sets $DISPLAY to some randomized path like
"/tmp/launch-madGzz/:0". Is it Apple's intention to break the
ancient convention for the local primary X screen (and if so, why
doesn't DISPLAY=":0.0" fail *all* the time)? Or is this a bug?
If it's a bug I'm afraid I don't know how to reproduce it, but will
keep looking if there's interest.
That's launchd's doing; it allows launchd to start X the first time it's needed. It's part of /System/Library/LaunchAgents/org.x.X11.plist. I'm guessing that if X is already running then :0.0 works.
Why does Apple do it that way? Speculation: because of Fast User Switching, OS X doesn't have the concept of the primary X screen. X isn't always running, and by the time it is it's too late to modify the DISPLAY variable for other running processes.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden