x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

nx-libx-3.5.0.17 differences
by Orion Poplawski 17 Jan '13

17 Jan '13

There are a lot of differences between nx-libs-3.5.0.16 and .17. I'm pointing some of them out here to make sure that they are intentional and to ask some questions. A bunch of Mesa headers are installed in /usr/include/nx/extras/. Are these needed? Hm, looks like they go in libnx-mesa-extras-dev. There are some Xtrans headers installed in /usr/include/nx/X11/Xtrans. Are these needed? If so, what library do they go with? Looks like the libraries that were in /usr/lib/nx/X11/locale/lib/common/: ximcp.so.2 xlcDef.so.2 xlcUTF8Load.so.2 xlibi18n.so.2 xlocale.so.2 xomGeneric.so.2 are now installed in /usr/lib/nx/X11 with "lib" prefixes. Are these needed? It's not obvious to me if they are packaged in debian or not. I can't tell if /usr/share/nx/SecurityPolicy is going in libnx-x11 or nxagent (or both)? Thanks... -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

2 2

Bug#101: x2goclient: resuming "running" session fails
by Ezra Bühler 16 Jan '13

16 Jan '13

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.

2 1

Bug#102: README.md files for each of the server folders
by Kjell Otto 16 Jan '13

16 Jan '13

Package: x2goserver Tag: patch

1 0

Bug#100:
by Christoph Mathys 16 Jan '13

16 Jan '13

I've tested with x2go client 4.0.0.1 on Ubuntu 12.04. The server is running 4.0.0.0-0~640~precise1, also Ubuntu 12.04. I don't observe an incresed CPU usage by the client while it is locked up.

3 3

Processed: your mail
by git-admin＠x2go.org 16 Jan '13

16 Jan '13

Processing commands for control(a)bugs.x2go.org: > retitle #100 X2GoClient locks up if connection with server gets disrupted Bug #100 [x2goclient] x2go client locks up on reboot or shutdown of server Changed Bug title to 'X2GoClient locks up if connection with server gets disrupted' from 'x2go client locks up on reboot or shutdown of server' > thanks Stopping processing here. Please contact me if you need assistance. -- 100: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=100 X2Go Bug Tracking System Contact git-admin(a)x2go.org with problems

1 0

Processed: your mail
by git-admin＠x2go.org 16 Jan '13

16 Jan '13

Processing commands for control(a)bugs.x2go.org: > severity #100 grave Bug #100 [x2goclient] x2go client locks up on reboot or shutdown of server Severity set to 'grave' from 'normal' > tag #100 confirmed Bug #100 [x2goclient] x2go client locks up on reboot or shutdown of server Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 100: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=100 X2Go Bug Tracking System Contact git-admin(a)x2go.org with problems

1 0

Processed: your mail
by git-admin＠x2go.org 16 Jan '13

16 Jan '13

Processing commands for control(a)bugs.x2go.org: > retitle 100 x2go client locks up on reboot or shutdown of server Bug #100 [x2goclient] (no subject) Set Bug title to 'x2go client locks up on reboot or shutdown of server'. > End of message, stopping processing here. Please contact me if you need assistance. -- 100: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=100 X2Go Bug Tracking System Contact git-admin(a)x2go.org with problems

1 0

nx-libs-3.5.0.17 whacky install
by Jan Engelhardt 15 Jan '13

15 Jan '13

Using the following... cat >"my_configure" <<-EOF #!/bin/sh -e %configure --disable-static EOF chmod a+x my_configure; make \ CONFIGURE=/home/abuild/rpmbuild/BUILD/nx-libs-3.5.0.17/my_configure \ PREFIX=/usr/PFX PROJECTROOT=/usr/PRJ INCLUDEDIR=/usr/include/nx \ USRLIBDIR=/usr/lib64/nx SHLIBDIR=/usr/lib64/nx (plus subsequent install with the same parameters) leads to some questionable results: Why do I get two Xcomp shared libraries (Xcomp.so.1 and Xcomp.so.3) that are equal anyway? /usr/PFX/lib/nx/X11/libXcomp.so /usr/PFX/lib/nx/X11/libXcomp.so.1 /usr/lib64/nx/libXcomp.a /usr/lib64/nx/libXcomp.so /usr/lib64/nx/libXcomp.so.3 /usr/lib64/nx/libXcomp.so.3.5.0 -rw-r--r-- 1 abuild abuild 1200469 Jan 6 18:25 ./usr/PFX/lib/nx/X11/libXcomp.so lrwxrwxrwx 1 abuild abuild 11 Jan 6 18:25 ./usr/PFX/lib/nx/X11/libXcomp.so.1 -> libXcomp.so lrwxrwxrwx 1 abuild abuild 17 Jan 6 18:20 ./usr/lib64/nx/libXcomp.so -> libXcomp.so.3.5.0 lrwxrwxrwx 1 abuild abuild 17 Jan 6 18:20 ./usr/lib64/nx/libXcomp.so.3 -> libXcomp.so.3.5.0 -rw-r--r-- 1 abuild abuild 1200469 Jan 6 18:25 ./usr/lib64/nx/libXcomp.so.3.5.0 There are three nxproxy instances rather than two: /usr/PFX/bin/nxproxy /usr/PFX/lib/nx/bin/nxproxy /usr/bin/nxproxy -rwxr-xr-x 1 abuild abuild 1158 Jan 4 12:25 ./usr/PFX/bin/nxproxy -rwxr-xr-x 1 abuild abuild 8753 Jan 6 18:25 ./usr/PFX/lib/nx/bin/nxproxy -rwxr-xr-x 1 abuild abuild 8753 Jan 6 18:25 ./usr/bin/nxproxy Something got really messed up here lately.

3 4

Bug#100:
by Christoph Mathys 15 Jan '13

15 Jan '13

Package: x2goclient The x2go-client seems to deadlock if I do a reboot/shutdown of the server. Some time after I initiated the reboot of the server the client asks if I want to terminate the session (because the servers does not respond), which I answer with yes. Nothing happens. When I try to close the session window, nothing happens. When I try to close the session using from the x2go client window by clicking the button to close the session, the client window itself starts to hang and I have to kill it.

2 1

Resuming "running" session
by Ezra Bühler 15 Jan '13

15 Jan '13

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.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev