[Xquartz-dev] DISPLAY issue

[Jeremy Huddleston]

Well the change to libxcb fixed things for libxcb and libX11... too bad ssh didn't parse the screen out of $DISPLAY like it's supposed to... =/  I have a workaround for that in libX11 now:

http://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=aae2a4a7aab26de3fa715d6ecd0a0e0926b37fc9

If we ever decide to support multiple X11 screens, we'll need to revert that (and have ssh fixed).

Here's a replacement for libX11.6.dylib with the workaround:
http://static.macosforge.org/xquartz/downloads/testing/libX11.6.dylib.bz2

(I won't be rolling an updated beta just to fix this... beta3 addressed the main issue, and the workaround is easy enough)

--Jeremy

On Apr 23, 2010, at 19:22, Louis Zulli wrote:

> 
> On Apr 23, 2010, at 9:52 PM, Tom Lane wrote:
> 
>> Only partially fixed, I'm afraid: remote clients over an ssh -Y tunnel
>> still fall over.  The complaints look like this:
>> 
>> connect /tmp/launch-9pq5dZ/org.macosforge.xquartz:0.0: No such file or directory
>> X connection to localhost:10.0 broken (explicit kill or server shutdown).
> 
> Yup, I'm seeing the same, after invoking ssh -Y from a local xterm:
> 
> LZsMacPro-OSX6: ~] xcalc
> connect /tmp/launch-FeMhCA/org.macosforge.xquartz:0.0: No such file or directory
> Error: Can't open display: localhost:10.0
> 
> 
> _______________________________________________
> Xquartz-dev mailing list
> Xquartz-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev