X2Go Bug report logs - #302
No session resume

Full log

Message #15 received at 302@bugs.x2go.org (full text, mbox, reply):

Received: (at 302) by bugs.x2go.org; 2 Apr 2014 16:21:16 +0000
From Borys.Saulyak@eumetsat.int  Wed Apr  2 18:21:15 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_BLOCKED,
	UNPARSEABLE_RELAY autolearn=ham version=3.3.2
X-Greylist: delayed 427 seconds by postgrey-1.34 at ymir; Wed, 02 Apr 2014 18:21:15 CEST
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.138])
	by ymir (Postfix) with ESMTPS id C7BA95DB16
	for <302@bugs.x2go.org>; Wed,  2 Apr 2014 18:21:15 +0200 (CEST)
Received: from [85.158.139.35:28987] by server-2.bemta-5.messagelabs.com id 90/2E-12074-0573C335; Wed, 02 Apr 2014 16:14:08 +0000
X-Env-Sender: Borys.Saulyak@eumetsat.int
X-Msg-Ref: server-2.tower-179.messagelabs.com!1396455247!27611149!1
X-Originating-IP: [193.17.11.201]
X-StarScan-Received:
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27545 invoked from network); 2 Apr 2014 16:14:07 -0000
Received: from mail5.eumetsat.int (HELO EXW05.eumetsat.int) (193.17.11.201)
  by server-2.tower-179.messagelabs.com with AES128-SHA encrypted SMTP; 2 Apr 2014 16:14:07 -0000
Received: from EXW04.eum.root.eumetsat.int (172.16.199.106) by
 exw05.eumetsat.int (172.28.0.11) with Microsoft SMTP Server (TLS) id
 8.3.327.1; Wed, 2 Apr 2014 18:13:57 +0200
Received: from EXW10.eum.root.eumetsat.int ([169.254.2.198]) by
 EXW04.eum.root.eumetsat.int ([172.16.199.106]) with mapi; Wed, 2 Apr 2014
 18:14:06 +0200
From: Borys Saulyak <Borys.Saulyak@eumetsat.int>
To: "302@bugs.x2go.org" <302@bugs.x2go.org>
Date: Wed, 2 Apr 2014 18:12:52 +0200
Subject: I think I found the way to reproduce it!
Thread-Topic: I think I found the way to reproduce it!
Thread-Index: AQHPTo5lXOH73vUHwkunKpTqEEBvow==
Message-ID: <A3ADF8C56ADA0F45BC34F904A6514E280151E8BBEB2C@EXW10.eum.root.eumetsat.int>
Accept-Language: en-US, en-IE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-IE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi guys,


I have quite often a problem to resume a session that was suspended after unexpected disconnect of the client.
In most of the cases it does not work.

On the client side I get this:
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Loop: PANIC! The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Loop: PANIC! The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Loop: PANIC! The remote NX proxy closed the connection.


On the server side I see this:
Apr  1 07:09:00 xxx /usr/local/bin/x2gosetkeyboard: Setting X keyboard according to /home/dadfmg/.x2go/C-dadfmg-77-1396335925_stDKDE_dp24/keyboard
Apr  1 07:11:32 xxx sshd[9739]: Accepted keyboard-interactive/pam for dadfmg from 10.10.1.13 port 59401 ssh2
Apr  1 07:11:34 xxx /usr/local/bin/x2gosuspend-session: session with ID dadfmg-77-1396335925_stDKDE_dp24 has been suspended successfully
Apr  1 07:11:36 xxx /usr/local/bin/x2goresume-session: client 10.10.1.13 has successfully resumed session with ID dadfmg-77-1396335925_stDKDE_dp24
Apr  1 07:11:36 xxx sshd[9742]: error: connect_to localhost port 30081: failed.
Apr  1 07:11:36 xxx sshd[9742]: channel_by_id: 0: bad id: channel free
Apr  1 07:11:36 xxx sshd[9742]: Disconnecting: Received ieof for nonexistent channel 0.

I am on the latest version of client/server.

I also noticed that I can achieve the same result if I suspend the session and then try to resume it by login in to the server via ssh and executing x2goresume-session <sessionid>
In this case even healthy and cleanly suspended session get screwed. 

So far I was not able to figure out how can I get the session back. It just does not work. I found a workaround for the time being which is to connect via local desktop (desktop sharing). This works even if session is screwed, but this is not what I want. I would like to get my session resumed correctly no matter what happened. Is this a known bug? Or is it only happening to me? I would really appreciate any help! X2GO is a great project and it has a great potential!

Thanks in advance for any help!

Send a report that this bug log contains spam.