X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
- Subject: X11 2.1.4 doesn't always respond to DISPLAY=":0.0"
- From: Tom Lane <email@hidden>
- Date: Mon, 17 Mar 2008 00:29:51 -0400
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.
regards, tom lane
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden