Hello everyone
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."
Is this the desired behavior? 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. Are there any thoughts on if and how this should be implemented?
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.
Hi Ezra,
this seems like a bug to me. Please report to
submit@bugs.x2go.org
Put "Package: x2goclient" into the first line of your mail.
Mike
On Di 15 Jan 2013 15:47:09 CET Ezra Bühler wrote:
Hello everyone
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."Is this the desired behavior? 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. Are there any thoughts on if and
how this should be implemented?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.
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
--
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.xf...