[Xquartz-dev] 2.5.1_beta2

[Jeremy Huddleston]

Ok.  I'm able to reproduce this now.

Thanks for your help debugging.  It'll be fixed in the next release.  I'll try to have one this weekend or early next week since this is a fairly bit usability issue that slipped through the cracks.

--Jeremy

On Apr 23, 2010, at 15:48, Jeremy Huddleston wrote:

> 
> On Apr 23, 2010, at 15:22, Tom Lane wrote:
> 
>> * If I launch Terminal then "echo $DISPLAY" shows the correct value
>> (with full path), even while shells inside xterms show the wrong value.
>> In fact, I can launch an xterm *from the Terminal shell* ("xterm &")
>> and its shell still shows the wrong value.
> 
> Ok, then it has nothing to do with the server.
> 
> That xterm is inheriting DISPLAY from its parent process (bash running in Terminal.app).
> 
> Can you launch xterm from Terminal.app through gdb and break on 'setenv' ... maybe we'll get lucky and see where it's getting changed...
> 
>> * I thought from the above that maybe xterm itself was incorrectly
>> editorializing on the DISPLAY value it inherited.  I tried reinserting
>> 2.5.0's /opt/X11/bin/xterm into a 2.5.1_beta2 installation, but this
>> did not fix it.  It is clear that something is changing the inherited
>> value of DISPLAY but it's not in the xterm executable --- maybe
>> somewhere in the X libraries?
> 
> These are the only changes 
> http://xquartz.macosforge.org/trac/wiki/ChangeLog
> 
> I updated libxcb, and I also changed libX11 to use libxcb for transport rather than the traditional route.  I bet somewhere in libxcb or libX11 there is some mangling of the DISPLAY environment variable...
> 
> As a workaround for now, you can probably just copy replace /opt/X11/lib/libX11.6.dylib with the one from 2.5.0. If that works, then it is either xcb itself or the xcb bits in libX11.
> 
> --Jeremy
> 
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev