[Xquartz-dev] 2.5.1_beta2

[robert delius royar]

Thu, 22 Apr 2010 (23:15 -0700 UTC) Jeremy Huddleston wrote:

>
> On Apr 22, 2010, at 16:09, robert delius royar wrote:
>
>> There appears to be a problem with the display variable.  Does the name have a '\r' or '\n' within it?  When I try to start gnuserv (for XEmacs), XEmacs (or gnuserv?) reports that it cannot find the port
>>
>> ,org.macosforge.xquartz.X11:6000
>
> My guess is that your apps are not using a recent libX11.  Are you building your own (very old) libX11 or using applications that were built and shipped with older versions of that library?

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
Here is what xrdb says:
/opt/X11/bin/xrdb: Invalid argument
/opt/X11/bin/xrdb: Can't open display 'org.macosforge.xquartz:0.0'

This is what XEmacs says (btw 'xemacs -nw' runs fine, so X is the 
problem);
Gui error: X server not responding
, "org.macosforge.xquartz:0.0"

An 'echo DISPLAY=$DISPLAY' command:
DISPLAY=org.macosforge.xquartz:0.0
otool -L xemacs-hg/src/xemacs (after make clean; make):
xemacs-hg/src/xemacs:
 	/usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0)
 	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
 	/opt/X11/lib/libpng14.14.dylib (compatibility version 16.0.0, current version 16.0.0)
 	/opt/X11/lib/libXpm.4.dylib (compatibility version 16.0.0, current version 16.0.0)
 	/opt/X11/lib/libXft.2.dylib (compatibility version 4.0.0, current version 4.13.0)
 	/opt/X11/lib/libXrender.1.dylib (compatibility version 5.0.0, current version 5.0.0)
 	/opt/X11/lib/libXt.6.dylib (compatibility version 7.0.0, current version 7.0.0)
 	/opt/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current version 11.0.0)
 	/opt/X11/lib/libX11.6.dylib (compatibility version 10.0.0, current version 10.0.0)
 	/opt/X11/lib/libSM.6.dylib (compatibility version 7.0.0, current version 7.1.0)
 	/opt/X11/lib/libICE.6.dylib (compatibility version 10.0.0, current version 10.0.0)
 	/opt/X11/lib/libfontconfig.1.dylib (compatibility version 6.0.0, current version 6.3.0)
 	/opt/local/lib/libgmp.10.dylib (compatibility version 11.0.0, current version 11.1.0)
 	/opt/local/lib/libtiff.3.dylib (compatibility version 13.0.0, current version 13.2.0)
 	/opt/local/lib/libjpeg.8.dylib (compatibility version 9.0.0, current version 9.1.0)
 	/opt/local/lib/libesd.0.dylib (compatibility version 3.0.0, current version 3.39.0)
 	/usr/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0)
 	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
 	/opt/X11/lib/libfreetype.6.dylib (compatibility version 11.0.0, current version 11.0.0)
 	/opt/X11/lib/libxcb.1.dylib (compatibility version 3.0.0, current version 3.0.0)
 	/opt/X11/lib/libXau.6.dylib (compatibility version 7.0.0, current version 7.0.0)
 	/opt/X11/lib/libXdmcp.6.dylib (compatibility version 7.0.0, current version 7.0.0)
 	/opt/X11/lib/libXaw.7.dylib (compatibility version 8.0.0, current version 8.0.0)
 	/opt/X11/lib/libXmu.6.dylib (compatibility version 9.0.0, current version 9.0.0)
 	/opt/local/lib/libgdbm.3.dylib (compatibility version 4.0.0, current version 4.0.0)
 	/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)
 	/opt/local/lib/libaudiofile.0.dylib (compatibility version 1.0.0, current version 1.2.0)
 	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.0)
 	/opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0)

When I reinstall beta1, 'echo $DISPLAY' shows
/tmp/launch-uO58xc/org.macosforge.xquartz:0

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.

Robert Royar

-- 
   You do people a bigger favor by giving them a few skills for figuring things
   out than by making them slaves to one particular program.
                                                               -Tari Fanderclai