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

Full log

🔗 View this message in rfc822 format

X-Loop: git-admin@x2go.org
Subject: Bug#101: x2goclient: resuming "running" session fails
Reply-To: Ezra Bühler <lists@easyb.ch>, 101@bugs.x2go.org
Resent-From: Ezra Bühler <lists@easyb.ch>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: git-admin@x2go.org
Resent-Date: Wed, 16 Jan 2013 13:48:02 +0000
Resent-Message-ID: <handler.101.B.13583439897653@bugs.x2go.org>
Resent-Sender: git-admin@x2go.org
X-X2Go-PR-Message: report 101
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.13583439897653
          (code B); Wed, 16 Jan 2013 13:48:02 +0000
Received: (at submit) by bugs.x2go.org; 16 Jan 2013 13:46:29 +0000
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171])
	by ymir (Postfix) with ESMTPS id F03305DB18
	for <submit@bugs.x2go.org>; Wed, 16 Jan 2013 14:46:28 +0100 (CET)
Received: by mail-wi0-f171.google.com with SMTP id hn14so3457642wib.10
        for <submit@bugs.x2go.org>; Wed, 16 Jan 2013 05:46:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-received:from:content-type:subject:message-id:date:to
         :mime-version:x-mailer:x-gm-message-state;
        bh=Ar/iwqEPRWBDtfJ3fAPM621fVe0OeZdpVXt/s4ukMtc=;
        b=KjFxUEoFmYnXnuze0HKZb47Ke8mfgORrydlAF85kb7JSZbFcncGrD53b4/NOGPitWi
         VQdm4T6/JYwbcigGrQCshqCgkj3Vh2h5eN3sfH+7MriOJhjT9AMPRo1fLmcL0SHJEC7L
         /jNq6yXieXGo6Eh7crRycbYUV0ZqRruV+I21c3H9I9SPsXW44MaM76qGJCHAzqHBIIDD
         XJVDvNBeS2wt8n483EWhYJT0eL5/JqgGWNkOjfMPHXaHOX6VVV32AyGDaYh/Ol+c2J1r
         AxL1KH9YAliI2mf8HRnBgVtRPRfz031Kt0895vUrBKQNzf/0Gwuoc1TeI/3vleP/a6FM
         8z5w==
X-Received: by 10.194.76.137 with SMTP id k9mr2352350wjw.29.1358343988605;
        Wed, 16 Jan 2013 05:46:28 -0800 (PST)
Received: from [10.0.0.4] (46-127-89-101.dynamic.hispeed.ch. [46.127.89.101])
        by mx.google.com with ESMTPS id t17sm9171918wiv.6.2013.01.16.05.46.27
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 16 Jan 2013 05:46:28 -0800 (PST)
From: Ezra Bühler <lists@easyb.ch>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B6C401CD-ECA7-4262-9780-E11C020A9830"
Message-Id: <00D261F4-59A9-48FF-A416-65253E076C60@easyb.ch>
Date: Wed, 16 Jan 2013 14:46:27 +0100
To: submit@bugs.x2go.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmr7hbxtQoCzEATLfU99FUwzOe7tKTpWkSk5H44iXbZkkV+eMQJxgIwVcRAEtpnTSLIrIj0

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

Package: x2goclient

Since commit 3335fca16afaa0792207228115e31630894dee71

(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.

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.

Here the complete transcript of an attempt to resume a running session:

read  1  sessions from config file 
start new ssh connection to server: "my.host.ch" : "22" krb:  false 

ssh connection ok 

continue normal x2go session 

Agent output: "gr_port=30127
sound_port=30128
fs_port=30129
" 
new gr_port:  "30127" 

new sound_port:  "30128" 

new fs_port:  "30129" 

starting nxproxy with:  "nxproxy -S nx/nx,options=/home/easyb/.x2go/S-easyb-90-1358245865_stDxterm_dp32/options:90" 

"
NXPROXY - Version 3.5.0

Copyright (C) 2001, 2010 NoMachine.
See 
http://www.nomachine.com/
for more information.

Info: Proxy running in client mode with pid '3771'.
" 

"Session: Starting session at 'Tue Jan 15 15:19:09 2013'.
Info: Connecting to remote host 'localhost:31127'.
Info: Connection to remote proxy 'localhost:31127' established.
" 

"channel_write failed"  -  "Remote channel is closed" 

"Error: The remote NX proxy closed the connection.
Error: Failure negotiating the session in stage '7'.
Error: Wrong version or invalid session authentication cookie.
Session: Terminating session at 'Tue Jan 15 15:19:09 2013'.
" 

"Session: Session terminated at 'Tue Jan 15 15:19:09 2013'.
" 

deleting proxy 

nxproxy not running 

proxy deleted 

checking exit status 
check command message 

"channel_open_session failed" :  "Received SSH_MSG_DISCONNECT: 33554432:Received ieof for nonexistent channel 0."


Cheers,
Ezra.

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.