#101 - x2goclient: resuming "running" session fails

X2Go Bug report logs - #101
x2goclient: resuming "running" session fails

Reported by: Ezra Bühler <lists@easyb.ch>

Date: Wed, 16 Jan 2013 13:48:02 UTC

Severity: normal

Tags: patch

Received: (at 101) by bugs.x2go.org; 16 Jan 2013 23:40:39 +0000
From mike.gabriel@das-netzwerkteam.de  Thu Jan 17 00:40:39 2013
Received: from freya.das-netzwerkteam.de (freya.das-netzwerkteam.de [88.198.48.199])
	by ymir (Postfix) with ESMTPS id 00AFD5DB18
	for <101@bugs.x2go.org>; Thu, 17 Jan 2013 00:40:39 +0100 (CET)
Received: from grimnir.das-netzwerkteam.de (grimnir.das-netzwerkteam.de [78.46.204.98])
	by freya.das-netzwerkteam.de (Postfix) with ESMTPS id C45DC9C7
	for <101@bugs.x2go.org>; Thu, 17 Jan 2013 00:40:38 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id B88CE3B90C
	for <101@bugs.x2go.org>; Thu, 17 Jan 2013 00:40:38 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at grimnir.das-netzwerkteam.de
Received: from grimnir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (grimnir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8olcxMoKfaQV for <101@bugs.x2go.org>;
	Thu, 17 Jan 2013 00:40:38 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id 8A8A43BA66
	for <101@bugs.x2go.org>; Thu, 17 Jan 2013 00:40:38 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
	by grimnir.das-netzwerkteam.de (Postfix) with ESMTP id 6E5D43B90C
	for <101@bugs.x2go.org>; Thu, 17 Jan 2013 00:40:38 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	grimnir.das-netzwerkteam.de
X-Spam-Flag: NO
X-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00,
	MIME_QP_LONG_LINE,URIBL_BLOCKED autolearn=ham version=3.3.1 running as userid=
X-Spam-Level: 
X-Spam-Bayes-Score: 0.0014
Received: by grimnir.das-netzwerkteam.de (Postfix, from userid 33)
	id 33DFA3BA60; Thu, 17 Jan 2013 00:40:37 +0100 (CET)
Received: from 106-135-142-46.pool.kielnet.net
 (106-135-142-46.pool.kielnet.net [46.142.135.106]) by
 mail.das-netzwerkteam.de (Horde Framework) with HTTP; Thu, 17 Jan 2013
 00:40:37 +0100
Message-ID: <20130117004037.12441fo4s1ivzkol@mail.das-netzwerkteam.de>
X-Priority: 3 (Normal)
Date: Thu, 17 Jan 2013 00:40:37 +0100
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
To: Ezra Bühler <lists@easyb.ch>
Cc: 101@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#101: x2goclient: resuming "running" session
 fails
References: <00D261F4-59A9-48FF-A416-65253E076C60@easyb.ch>
In-Reply-To: <00D261F4-59A9-48FF-A416-65253E076C60@easyb.ch>
MIME-Version: 1.0
Content-Type: multipart/signed;
 boundary="=_1cv5bw62273p";
 protocol="application/pgp-signature";
 micalg="pgp-sha1"
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.4)

[Message part 1 (text/plain, inline)]

Hi Ezra, On Mi 16 Jan 2013 14:46:27 CET Ezra Bühler wrote: > Since commit 3335fca16afaa0792207228115e31630894dee71 there was a follow-up commit to the one you quote: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=a2d95c0c106923162bb510c88806b7384786b97d > (X2Go resume session slot: double click on a selected session is > supposed to resume that session. To make this feature functional for > running sessions the session has to be suspended first.) > > resuming a "running" session (by double clicking it) is no longer > possible unless you press suspend first. On Linux I get following > error: > > "channel_open_session failed" : "Received SSH_MSG_DISCONNECT: > 33554432:Received ieof for nonexistent channel 0." > > I am used to closing the client without explicitly suspending the > session. This leaves the session marked as "running". When I start > up the client again I want to be able to resume the session with the > least effort as possible. In my opinion the right way to achieve > this behavior would be to suspend the session when the client quits. Unless you shoot the client with kill -9 it should indeed run x2gosuspend-session on the server before quitting. I would consider that as a minor bug, as well. > In my opinion simply restoring the behavior we had prior to > 3335fc... would be wrong. Because when trying to resume a "running" > session the "resume" button in the session dialog dialog would not > be active, but resuming by double clicking still possible, which I > find misleading. Double clicking the session should work. So should the resume button. Resuming of a running session should be a sequence of x2gosuspend-session call on the server and then a x2goresume-session call for that same session. Between the two calls you need some time for the session to change its state (couple of secs). > Here the complete transcript of an attempt to resume a running session: > > [...] If you could come up with a patch, that would be really helpful. The last patch you sent was accepted. So will be a follow-up patch (at least it's very likely!!!). > Cheers, > Ezra. > Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

X2Go Developers <owner@bugs.x2go.org>. Last modified: Tue Dec 3 18:56: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/.

X2Go Bug report logs - #101 x2goclient: resuming "running" session fails

X2Go Bug report logs - #101
x2goclient: resuming "running" session fails