Received: (at submit) by bugs.x2go.org; 13 Dec 2012 05:42:51 +0000 Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by ymir (Postfix) with ESMTPS id 5F94D5DA6B for ; Thu, 13 Dec 2012 06:42:51 +0100 (CET) Received: by mail-vb0-f51.google.com with SMTP id fq11so1668381vbb.24 for ; Wed, 12 Dec 2012 21:42:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=Q993cvrm/XhohAXX0/iGE7nWwrcxMaJSs2bPY7XpTt4=; b=V+Tj/SEas2LvZTp15epdBEJbCo1vv1i+NAhKDI++m7xuu5cv/3PvnNXwujwiuzQZW3 lNd7cpoV08zBSO1kVYKPbzD3TfmTuoPDU9UqF19FskdsfdytkVgGZ/v6gnmrUjcdl1cm S5/hdPSxZiUWtvOQ5RGAImoPZPno52nyU+qUTarElzWGwWxLIB/A2NfVNY82iSBO2toU /Kjpmrx+0KHN4f8/rUSzpZoaBtnAWXtsmrNHSp+JJMxpSZW7EqyDPceMpys8jiP+gDeK F09JZkogX5MZk/5idULnz3/RLoZJUogZnXfAVgfqnS9vRI+n9r8wBK7ofliOqAu43L8R m9mQ== Received: by 10.52.22.240 with SMTP id h16mr974933vdf.82.1355377369872; Wed, 12 Dec 2012 21:42:49 -0800 (PST) MIME-Version: 1.0 Sender: martincigorraga@gmail.com Received: by 10.58.212.161 with HTTP; Wed, 12 Dec 2012 21:42:09 -0800 (PST) From: =?ISO-8859-1?Q?Mart=EDn?= Cigorraga Date: Thu, 13 Dec 2012 02:42:09 -0300 X-Google-Sender-Auth: 5qy9SEuvfTPu7EZjlDyVMFcDx-Q Message-ID: Subject: Package: x2gosuspend-session executes with no SESSION_NAME set To: submit@bugs.x2go.org Content-Type: multipart/alternative; boundary="20cf3079bb0aaaf9f304d0b562b3" --20cf3079bb0aaaf9f304d0b562b3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message ---------- From: Mart=C3=ADn Cigorraga 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 o= ne > 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 u= se > (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. --20cf3079bb0aaaf9f304d0b562b3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ----------<= br>From: Mart=C3=ADn 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-netzwer= kteam.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 x= 2go server? I find that from time to time it tends to break leaving my prev= iously
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opened sessions orphan - th= ere's no way to attach to them any more. This is the error message i ju= st get while trying to connect with one of my
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sessions running awesomewm:=
04:23 < msx> "Connection failed Died at /usr/lib/x2go/x2gogetage= nt line 33. Died at /usr/lib/x2go/x2gochangestatus line 35. ERROR: failed t= o suspend session
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0with ID Died at /usr/lib/x2= go/x2gochangestatus line 35. argument "session_id" missed at /usr= /lib/x2go/x2godbwrapp= er.pm line 575."
04:24 < msx> the thing is that the session on the server seems to sti= ll 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 i= ssue 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

<= br>
Hello Mike, thanks for being aware of this issue.=C2=A0=
These are the software versions of the x2go software I'm en= joying:
x2goserver 3.1.1.4-2
x2goclient 3.99.2.2-1=C2=A0

Regarding pyhoca-* I was kindly pointed to the x2go website by ano= ther 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 so= me 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/bi= n/python2 in contrast to most other distros (and Python 3 /usr/bin/python) = and thus breaking compatibility with all the Python 2 scripts created outsi= de AL. This issue is really easy to resolve, I just need a couple of free h= ours to figure it out and test that everything works okay and then I will p= ack pyhoca for Arch.


--20cf3079bb0aaaf9f304d0b562b3--