[X2go-Dev] Can not use FreeNX alongside latest X2Go packages (was: Client-side printing not working (most likely due to the x2goserver-printing package being unavailable for installation))

[Stefan Baur]

During my debug session, I noticed that these two packages:
> ii libxcompext3 1:3.5.0-1-0~x2go-bpo1+lenny~main~36~build1 NX X11 
> protocol compression extensions library
> ii libxcompshad3 3.5.0-2-0~x2go-bpo1+lenny~main~24~build1 NX shadowing 
> library
also had the "x2go-bpo1+lenny"-tag that was causing confusion with 
regards to
> ii x2goserver 3.0.99.8-0~x2go-bpo1+lenny~main~388~build1 X2go server 
> daemon scripts
> ii x2goserver-extensions 3.0.99.8-0~x2go-bpo1+lenny~main~388~build1 
> X2go server daemon scripts (extensions)
(where I wanted to use squeeze packages so x2goserver-printing would 
become installable)

So I tried uninstalling and reinstalling them.
Trying to uninstall them, I got a warning that this would uninstall the 
FreeNX packages as well, so I repackaged all of the named packages (freenx
freenx-media, freenx-session-launcher, freenx-rdp, freenx-server, 
freenx-vnc, nxagent, x2goserver-printing, x2goserver-extensions, 
x2goserver, x2goagent) using dpkg-repack just to be safe.

After that, I proceeded with the uninstall/reinstall and re-added the 
FreeNX packages.
Now, FreeNX refuses to connect - X2Go still connects fine, though.
The FreeNX error message is: "Session startup failed", with the 
following Details provided:
NX> 203 NXSSH running with pid: 5180
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.2.84 on port: 443
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: unlimited1
NX> 102 Password:
NX> 103 Welcome to: myservernamehere1 user: unlimited1
NX> 105 listsession --user="unlimited1" --status="suspended,running" 
--geometry="1366x768x32+render" --type="unix-application"
NX> 127 Sessions list of user 'unlimited1' for reconnect:

Display Type             Session ID                       Options  Depth 
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- ----- 
-------------- ----------- ------------------------------


NX> 148 Server capacity: not reached for user: unlimited1
NX> 105 startsession  --rootless="1" --virtualdesktop="0" 
--application="/usr/local/bin/starter" --link="wan" --backingstore="1" 
--encryption="1" --cache="16M" --images="0M" --shmem="1" --shpix="1" 
--strict="0" --composite="1" --media="0" --session="test2" 
--type="unix-application" --client="winnt" --kbload=" --kbload=pc105/de" 
--keymap=" --keymap=de" --keyboard="pc105/de" --aux="1" 
--screeninfo="1096x700x32+render"

NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 3.3.0)
NX> 700 Session id: myservernamehere1-1000-629950A11DE87FB68440D5DDA0B4BB76
NX> 705 Session display: 1000
NX> 703 Session type: unix-application
NX> 701 Proxy cookie: 72d13ef04406e96020c33890c4ca51c3
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 72d13ef04406e96020c33890c4ca51c3
NX> 704 Session cache: unix-application
NX> 707 SSL tunneling: 1
/usr/lib/nx/nxserver: Zeile 1569:  9214 Beendet                 sleep 
$AGENT_STARTUP_TIMEOUT
NX> 105 NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set 
SESSION_LOG_CLEAN=0 in node.conf and investigate 
"/home/unlimited1/.nx/F-C-myservernamehere1-1000-629950A11DE87FB68440D5DDA0B4BB76/session". 
You might also want to try: ssh -X myserver; /usr/lib/nx/nxnode --agent 
to test the basic functionality. Session log follows:
Can't open 
/var/lib/nxserver/db/running/sessionId{629950A11DE87FB68440D5DDA0B4BB76}: Datei 
oder Verzeichnis nicht gefunden.
NX> 280 Exiting on signal: 15

I thought X2Go was supposed to be usable in parallel, so it seems 
something broke from one version to the next.
Is this the end for concurrent installations, or is it possible to make 
both work in parallel again?

Kind Regards,
Stefan