[Xquartz-dev] 2.5.1_beta2

[robert delius royar]

Fri, 23 Apr 2010 (11:20 -0700 UTC) Jeremy Huddleston wrote:

>
> On Apr 23, 2010, at 08:02, robert delius royar wrote:
>
>> I reinstalled beta2 to get a listing of the errors.  On my installation, the directory that holds the display is not prepended to the display's name.  That appears to explain all of the errors I was seeing.
>>
>> In an xterm 'echo $DISPLAY' returns org.macosforge.xquartz.X11:0.0
>
> That is wrong.  It should be something like:
>
> /tmp/launch-31i9qn/org.macosforge.xquartz:0
>
>> When I reinstall beta1, 'echo $DISPLAY' shows
>> /tmp/launch-uO58xc/org.macosforge.xquartz:0
>
> That is the correct $DISPLAY
>
>> The odd thing (to me) is that xterms work fine, and surely it needs to know the correct DISPLAY.  Also, another poster mentioned that on his system, his display includes the directory.  I have checked my startup files (.tcshrc and xstartup); neither sets the display.  This is a new MBP, so there shouldn't be other things interfering, plus beta1 (and the last update release) both work.
>
>
> Can you try creating a new user account:
>
> Install 2.5.1_beta2.
OK 
> Create a new user in User Preferences
OK
> Log out as the current user and log in as the other (or use FUS)
Tried both
> Launch XQuartz.app
DISPLAY=org.macosforge.xquartz.X11:0.0
in the new user account.
When I use FUS, I switched back to my regular account and see 
DISPLAY=/tmp/launch-uO58xc/org.macosforge.xquartz:0
in terminal (without having started Xquartz.app or an X application in 
that account).  Also, I have the Xquartz icon permanently in my dock 
(set that way).  It shows the dot beneath it to indicate it is running. 
I can select the icon and get the X11 menu bar.  Xterms run from it, but 
not my own apps (XEmacs or Alpine within an xterm.

I believe that it is also odd that the display variable is the same 
socket I had this morning even though I have exited Xquartz a few times 
and have logged out.

You asked others to supply the reults of grepping system.log for 
DISPLAY.  Here, are my results of that (I think the erroneous perios 
are 15:XX times:
Apr 23 08:33:58 grendal [0x0-0x13013].org.macosforge.xquartz.X11[182]: 
X11.app: Received new $DISPLAY fd: 5 ... sleeping to allow xinitrc to 
catchup.
Apr 23 10:00:24 grendal [0x0-0x2f02f].org.macosforge.xquartz.X11[1023]: 
X11.app: Received new $DISPLAY fd: 5 ... sleeping to allow xinitrc to 
catchup.
Apr 23 10:39:49 grendal [0x0-0x46046].org.macosforge.xquartz.X11[10288]: 
X11.app: Received new $DISPLAY fd: 5 ... sleeping to allow xinitrc to 
catchup.
Apr 23 15:38:31 grendal [0x0-0x93093].org.macosforge.xquartz.X11[12283]: 
X11.app: Received new $DISPLAY fd: 6 ... sleeping to allow xinitrc to 
catchup.
Apr 23 15:44:39 grendal org.macosforge.xquartz.startx[12504]: X11.app: 
Received new $DISPLAY fd: 5 ... sleeping to allow xinitrc to catchup.
Apr 23 15:53:53 grendal [0x0-0xab0ab].org.macosforge.xquartz.X11[12917]: 
X11.app: Could not connect to server 
(DISPLAY="/tmp/launch-uO58xc/org.macosforge.xquartz:0", unsetting). 
Starting X server.
Apr 23 15:53:53 grendal [0x0-0xab0ab].org.macosforge.xquartz.X11[12917]: 
X11.app: No launchd socket handed off, unsetting DISPLAY
Apr 23 15:55:46 grendal [0x0-0xc20c2].org.macosforge.xquartz.X11[13196]: 
X11.app: Received new $DISPLAY fd: 8 ... sleeping to allow xinitrc to 
catchup.


>
>
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
>

-- 
  rdr