[X2Go-User] Session Resume fails with 4.0.1.19-0~1062~ubuntu14.10.1

[richter at ecos.de]

Hi Mihai,

> 
> That's SIGHUP. I can only speculate that x2goagent died?
> 

But it is happening after about 60sec, so it looks more like a timeout...

> 
> Regarding X2Go Client... it does not create a debug log. You have to do
that
> yourself. It's as easy as starting x2goclient.exe with --debug > debug.log
> 2>&1 from cmd.exe. Make sure to cd into the directory where you want to
> have the debug.log written and use the correct path to x2goclient.exe.
> 

Ok, done this and here is the result, both with the same windows client
4.0.3.2.

--> Not working:

x2go-DEBUG-onmainwindow.cpp:9334> Port is free: 31001
x2go-DEBUG-sshprocess.cpp:294> Starting tunnel via SshProcess object (3):
"localhost":30001 -> "localhost":31001

x2go-DEBUG-onmainwindow.cpp:5172> Waiting for win-servers.
Object::connect: No such slot ONMainWindow::slotTunnelOk()
x2go-DEBUG-sshprocess.cpp:157> Direct tunnel: waiting for connections on
"localhost":31001


--> Working:

x2go-DEBUG-onmainwindow.cpp:9334> Port is free: 31033
x2go-DEBUG-sshprocess.cpp:294> Starting tunnel via SshProcess object (3):
"localhost":30033 -> "localhost":31033

x2go-DEBUG-onmainwindow.cpp:9312> got localhost
x2go-DEBUG-onmainwindow.cpp:9340> Port already used: 6000
x2go-DEBUG-onmainwindow.cpp:5337> "Starting NX proxy, command: nxproxy -S
nx/nx,options=/cygdrive/C/Users/Gerald/X2GO~1/S-1F32~1/options:60"
x2go-DEBUG-sshprocess.cpp:157> Direct tunnel: waiting for connections on
"localhost":31033

So NX proxy is never started in case it is not working.

Looks like Bug#804, so I tested
http://code.x2go.org/releases/binary-win32/x2goclient/tmp/x2goclient-4.0.4.0
-2015.03.10-ffc56f3-setup.exe and it works :-)

Thanks very much for your work on x2go! It's a great tool!

Regards

Gerald