X2Go Bug report logs - #82
x2gosuspend-session executes with no SESSION_NAME set

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Date: Wed, 12 Dec 2012 11:03:01 UTC

Severity: normal

Tags: pending

Fixed in version 4.1.0.0

Done: X2Go Release Manager X2Go Release Manager <git-admin@x2go.org>

Bug is archived. No further changes may be made.

Full log


🔗 View this message in rfc822 format

X-Loop: git-admin@x2go.org
Subject: Bug#82: Fwd: Message with no Package: tag cannot be processed! (Package: x2gosuspend-session executes with no SESSION_NAME set)
Reply-To: Martin Cigorraga <martincigorraga@gmail.com>, 82@bugs.x2go.org
Resent-From: Martin Cigorraga <martincigorraga@gmail.com>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: git-admin@x2go.org
Resent-Date: Thu, 13 Dec 2012 18:33:02 +0000
Resent-Message-ID: <handler.82.B82.135542353526784@bugs.x2go.org>
Resent-Sender: git-admin@x2go.org
X-X2Go-PR-Message: followup 82
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by 82-submit@bugs.x2go.org id=B82.135542353526784
          (code B ref 82); Thu, 13 Dec 2012 18:33:02 +0000
Received: (at 82) by bugs.x2go.org; 13 Dec 2012 18:32:15 +0000
Received: from mail-yh0-f42.google.com (mail-yh0-f42.google.com [209.85.213.42])
	by ymir (Postfix) with ESMTPS id 443435DA6B
	for <82@bugs.x2go.org>; Thu, 13 Dec 2012 19:32:15 +0100 (CET)
Received: by mail-yh0-f42.google.com with SMTP id g71so557135yhg.1
        for <82@bugs.x2go.org>; Thu, 13 Dec 2012 10:32:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=from:to:subject:date:message-id:organization:user-agent
         :mime-version:content-type:content-transfer-encoding;
        bh=zxbfsiRvG81bDgKxwf9cYFo1PUZK+fjTLiUVkmZbuzg=;
        b=HfhTMr2O+LFiD4lVBrqSj86PlNhUsDT5uOBaEB+kb2hmGTmsep6Tu3hTRCfTLuDMzi
         rc2bvhdbBcrfl9tV1GzK98fpzx6iC6Hi4BfoKr3jIje0oRBKphtg0DdT9dhvwTY57Em+
         siPtPKLjH6JfWP3mrJDVo/6Zg4SiDJx/qRUBWkQH1NKuiXpFMbWdYs3+ViIpy9B5+U2b
         Q/9WzQgICWdVIXBBk7IgzJmsasbxcxx2+WQUklrOu47NZGTNPkI5Usd0YEe8MKWTzsl8
         jX7ipls28bOwLADMOobOrt1YhFSXjuUQiiYx+51vj1CMY+BQ27Jqx71irBRgnVi90KjO
         9hxw==
Received: by 10.236.149.100 with SMTP id w64mr2777478yhj.125.1355423533803;
        Thu, 13 Dec 2012 10:32:13 -0800 (PST)
Received: from heybeavis.localnet ([190.193.16.81])
        by mx.google.com with ESMTPS id g3sm1930675ani.18.2012.12.13.10.31.30
        (version=SSLv3 cipher=OTHER);
        Thu, 13 Dec 2012 10:32:12 -0800 (PST)
From: Martin Cigorraga <martincigorraga@gmail.com>
To: 82@bugs.x2go.org
Date: Thu, 13 Dec 2012 15:25:14 -0300
Message-ID: <1444547.zmbIeJ0bh1@heybeavis>
Organization: EDGE IT
User-Agent: KMail/4.9.4 (Linux/3.6.9-1-ARCH; KDE/4.9.4; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nextPart1697832.xfkRhtXO3F"
Content-Transfer-Encoding: 7Bit
[Message part 1 (text/plain, inline)]
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.
[forwarded message (message/rfc822, inline)]
From: X2Go Bug Tracking System <git-admin@x2go.org>
To: Martín Cigorraga <msx@archlinux.us>
Subject: Message with no Package: tag cannot be processed! (Package: x2gosuspend-session executes with no SESSION_NAME set)
Date: Thu, 13 Dec 2012 05:48:02 +0000
[Message part 3 (text/plain, inline)]
Your message didn't have a Package: line at the very first line of the
mail body (part of the pseudo-header), or didn't have a Package: line
at all. Unfortunatly, this means that your message has been ignored
completely.

Without this information we are unable to categorise or otherwise deal
with your problem report. Please _resubmit_ your report to
submit@bugs.x2go.org and tell us which package the
report is for. For help, check out
http://bugs.x2go.org/Reporting.html.

Your message was dated Thu, 13 Dec 2012 02:42:09 -0300 and had
message-id <CAJLw8+Uim7jOKTcOmVbAi6+cPaYN6bhgMCJMLtNeL6zFGpXzPQ@mail.gmail.com>
and subject Package: x2gosuspend-session executes with no SESSION_NAME set.
The complete text of it is attached to this message.

If you need any assistance or explanation please contact
git-admin@x2go.org and include the the attached
message.

If you didn't send the attached message (spam was sent forging your
from address), we apologize; please disregard this message.

-- 
-1: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=-1
X2Go Bug Tracking System
Contact git-admin@x2go.org with problems
[Message part 4 (message/rfc822, inline)]
From: Martín Cigorraga <msx@archlinux.us>
To: submit@bugs.x2go.org
Subject: Package: x2gosuspend-session executes with no SESSION_NAME set
Date: Thu, 13 Dec 2012 02:42:09 -0300
[Message part 5 (text/plain, inline)]
---------- 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.
[Message part 6 (text/html, inline)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Mar 28 10:04:02 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.