---------- Forwarded message ----------
From: Martín Cigorraga <msx@archlinux.us>
Date: Thu, Dec 13, 2012 at 1:24 AM
Subject: x2gosuspend-session executes with no SESSION_NAME set
To: submit@bugs.x2go.org


On Wed, Dec 12, 2012 at 8:01 AM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Package: x2goserver
Severity: normal
Tag: moreinfo

User msx on IRC reported the below issues on IRC:

04:23 < msx> hi all! is anyone else having erratic behaviour of the x2go server? I find that from time to time it tends to break leaving my previously
             opened sessions orphan - there's no way to attach to them any more. This is the error message i just get while trying to connect with one of my
             sessions running awesomewm:
04:23 < msx> "Connection failed Died at /usr/lib/x2go/x2gogetagent line 33. Died at /usr/lib/x2go/x2gochangestatus line 35. ERROR: failed to suspend session
             with ID Died at /usr/lib/x2go/x2gochangestatus line 35. argument "session_id" missed at /usr/lib/x2go/x2godbwrapper.pm line 575."
04:24 < msx> the thing is that the session on the server seems to still be alive, it's just the x2go client can't attach to it

@msx: what exact version of X2G Server are you using? The reason for this issue can also be in the X2Go client being used. So, what client do you use (x2goclient, pyhoca-*) and what version of that client?

Greets,
Mike


Hello Mike, thanks for being aware of this issue. 
These are the software versions of the x2go software I'm enjoying:
x2goserver 3.1.1.4-2
x2goclient 3.99.2.2-1 

Regarding pyhoca-* I was kindly pointed to the x2go website by another IRC user to learn about it and since it isn't already packaged in my GNU/Linux distribution (Arch Linux) I was planning to add it; however some errors at compile time what I don't have the time right now to debug[0] made it impossible to install & run the application.
Please let me know if you need further feedback from my part.

[0] From the glimpse I gave to the errors it seems it's related to the way Python 2 is packaged here in Arch, being named /usr/bin/python2 in contrast to most other distros (and Python 3 /usr/bin/python) and thus breaking compatibility with all the Python 2 scripts created outside AL. This issue is really easy to resolve, I just need a couple of free hours to figure it out and test that everything works okay and then I will pack pyhoca for Arch.