NX fails to start

[alphapapa]

This was mentioned in #198 but it seems like it was overlooked.

NXAGENT - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '8227'.
Session: Starting session at 'Wed Oct  3 00:44:12 2012'.
Error: Aborting session with 'Unable to open display 'nx/nx,options=/home/me/.winswitch/server/sessions/72/nx_options.txt:72''.
Session: Aborting session at 'Wed Oct  3 00:44:12 2012'.
Session: Session aborted at 'Wed Oct  3 00:44:12 2012'.

Why is all that extra stuff being sent to NX for the display, instead of it just being ":72"?

winswitch:
  Installed: 0.12.16-4
  Candidate: 0.12.16-4
  Version table:
 *** 0.12.16-4 0
        500 http://winswitch.org/ precise/main i386 Packages
        100 /var/lib/dpkg/status

[Antoine Martin]

Why is all that extra stuff being sent to NX for the display, instead of it just being ":72"?

That is just how NX works.

Why NX fails to start is not clear, "Unable to open display" is rather vague - I will try it in a Precise VM (that's precise amd64 up to date at both ends I suppose?)

[alphapapa]

Hm, ok. Well, I have the packages from nomachine installed, so I had to symlink the executables to /usr/bin, and then symlink the libraries to /usr/lib one-by-one until it stopped giving library errors. I tried using LD_LIBRARY_PATH but that caused errors in Python about being unable to determine the version of some of the libraries.

I have amd64 on two systems, but the one I was using in this case was i386.

I don't know if this is worth your time looking into. What is the recommended way to install NX for using with Winswitch? Maybe that's the problem.

Thanks.

[Antoine Martin]

closing, xpra is the way forward and I don't want to start fighting with the various weird packaging that distros / NX do.