[9fans] Plan9port GUI applications don't work in Nx session

[Aram Hăvărneanu]

I have a Windows machine that runs an X server and a Linux machine
running plan9port. When I use the Windows machine to connect to the
Linux machine via ssh, with X forwarding enabled, plan9port GUI
applications like acme and sam work perfectly. In this case the
environment is:

SSH_CLIENT=192.168.0.10 58970 22
SSH_CONNECTION=192.168.0.10 58970 192.168.0.12 22
DISPLAY=localhost:10.0

Nx is a technology that runs an X server proxy both on the server and
on the client, proxy that serves requests locally when it can and
batches requests reducing the number of round trips tremendously.
I've seen X applications that did tens of thousand of X requests do
only 20 requests on the wire with Nx. It's usable even on dial up.
There's a commercial implementation: http://www.nomachine.com and two
open source implementations, FreeNX: http://freenx.berlios.de and one
by Google, Neatx: http://code.google.com/p/neatx .

Plan9port applications don't work in Nx, for some reason. The environment is:

SSH_CLIENT=::1 41980 22
DISPLAY=:1011.0

Acme errors with:

X error: error_code=8, request_code=1, minor=0 disp=1d72230
BadMatch (invalid parameter attributes)
X error: error_code=3, request_code=8, minor=0 disp=1d72230
BadWindow (invalid Window parameter)
X error: error_code=3, request_code=3, minor=0 disp=1d72230
BadWindow (invalid Window parameter)
XGetWindowAttributes failed
X error: error_code=4, request_code=54, minor=0 disp=1d72230
BadPixmap (invalid Pixmap parameter)
X error: error_code=3, request_code=2, minor=0 disp=1d72230
BadWindow (invalid Window parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
X error: error_code=13, request_code=56, minor=0 disp=1d72230
BadGC (invalid GC parameter)
9pserve: announce unix!/tmp/ns.aram.:1011/acme: Address already in use
acme: can't post service: 9pserve failed

I don't know if this is an X error, or a Plan9 environment error. I
have this in my /tmp:

r60% ls -d /tmp/ns*
/tmp/ns.aram.:1011
/tmp/ns.aram.localhost:10

The 'localhost' string is missing, because $DISPLAY doesn't have it.
Does this confuse plan9port? In /tmp/ns.aram.:1011 I have:

r60:~$ ls -l /tmp/ns.aram.:1011
total 0
srwxr-xr-x 1 aram aram 0 2012-01-14 14:10 acme=
srwxr-xr-x 1 aram aram 0 2012-01-14 14:10 plumb=

Any tips? Thanks,

[Aram Hăvărneanu]

Post by Aram Hăvărneanu
I don't know if this is an X error, or a Plan9 environment error.

If I set $NAMESPACE before starting acme, I only get the X errors, so
I guess the problem is X related.

[Aram Hăvărneanu]

Post by Aram Hăvărneanu

Post by Aram Hăvărneanu
I don't know if this is an X error, or a Plan9 environment error.

If I set $NAMESPACE before starting acme, I only get the X errors, so
I guess the problem is X related.

I upgraded to the latest, beta, version of the commercial Nx server
and the problem went away. I guess the proxy implemented a version of
the X protocol that was too old.