I can't start an NX or VNC session. Can't see why VNC is failing, but NX is failing because of extra data in the DISPLAY var.

VNC server.log: ​http://kpaste.net/f7e1222 VNC vnc.log: ​http://kpaste.net/67fa5f

NX server.log: ​http://kpaste.net/cd2d7 NX nx.log: ​http://kpaste.net/a99a

NX server is NoMachine's NX v3.5.0 VNC is RealVNC Enterprise v4.6.3

Many unit tests fail to load because they can't find their modules:

Traceback (most recent call last): 
  File "tests/window_xlib_test.py", line 8, in <module> 
    from winswitch.util.simple_logger import Logger 
ImportError: No module named winswitch.util.simple_logger 

Perhaps there is a more elegant way to fix that what I did in the attached patch, but it works for me.

Thanks.

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