x2go-dev January 2013

x2go-dev@lists.x2go.org

30 participants
63 discussions

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

Bug#98: Git IRC hook
by Kjell Otto 10 Jan '13

10 Jan '13

This is a good start: https://wiki.icinga.org/display/community/GIT+Commit+Bot And should probably be combined with this: https://gist.github.com/1821358 would not even need ruby Greetings, Kjellski

1 0

Bug#44:
by Lukas 09 Jan '13

09 Jan '13

Hi, I think, I experienced this bug as well (same kind of backtrace). In my case this happened, when installing nxproxy and x2goclient in a non standard place which is not on the path. The client tries to start nxproxy which fails. x2goclient never checks, if the start suceeded or not (see x2goclient-4.0.0.1/onmainwindow.cpp, lines: 3135, 5065). Workaround: add nxproxy to $PATH. Best, Lukas

1 0

Bug#84: Hardcoded -O3 in CFLAGS
by Bernard Cafarelli 09 Jan '13

09 Jan '13

Regarding the optflags patch, is it possible to drop altogether the hardcoded "-O3" in C/CXXFLAGS in the various configure.in? This would remove the need for 4 autoreconf when using another optimization level -- Bernard Cafarelli (Voyageur) Gentoo developer (NX, GNUstep, net-misc, llvm/clang, ...)

4 9

Bug#28: Xfixes issues with Ubuntu precise and above
by Mike Gabriel 09 Jan '13

09 Jan '13

Re-opening this issue as it is not 100% solved and understood... The situation is: with extensions XFIXES enabled in nxagent/x2goagent we observe KDE crashes on Ubuntu precise and above. The crashes happen in kwin. The problem could be tracked down to some problems in libxfixes. The change must have been between libxfixes from oneiric and libxfixes from precise. On IRC I wrote this about the observed issue: 15:48 < sunweaver> siretart: I might have found the libxfixes issue with libxfixes since precise... 15:48 < sunweaver> at least I have several question marks... 15:49 < sunweaver> the xserver-xorg src package in precise has a patch named: 500_pointer_barrier_thresholds.diff 15:50 < sunweaver> this patches in xfixes v6 code into the xfixes v5 extension 15:51 < sunweaver> in that patch you can also see that the xfixes extension version is also incremented (5 -> 6) 15:52 < sunweaver> the libxfixes 1:5.0-4ubuntu4 and the package x11proto-fixes-dev 1:5.0-2ubuntu1 package also have patches for this improvement: both named 01_fixesproto-v6.diff. 15:54 < sunweaver> However, when looking at a build of libxfixes 5.0-4ubuntu4 I see a config.h file that announces itself with PACKAGE_VERSION 5.0. 15:55 < sunweaver> So, my current guess is that libxfixes annouces itself as v5 and also does a xlib-xserver version handshake based on v5, but then executes code from libxfixes v6 which then breaks nxagent. 15:55 < sunweaver> Is that possible? Can anyone comment on this? Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Processed: Xfixes issues with Ubuntu precise and above
by git-admin＠x2go.org 09 Jan '13

09 Jan '13

Processing commands for control(a)bugs.x2go.org: > unarchive #28 Bug #28 {Done: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>} [x2goserver] x2go kubuntu 12.4 Unarchived Bug 28 > reopen #28 Bug #28 {Done: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>} [x2goserver] x2go kubuntu 12.4 Bug reopened Ignoring request to alter fixed versions of bug #28 to the same values previously set > retitle #28 Xfixes issues with Ubuntu precise and above Bug #28 [x2goserver] x2go kubuntu 12.4 Changed Bug title to 'Xfixes issues with Ubuntu precise and above' from 'x2go kubuntu 12.4' > thanks Stopping processing here. Please contact me if you need assistance. -- 28: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=28 X2Go Bug Tracking System Contact git-admin(a)x2go.org with problems

1 0

Bug#97: This issue has already been fixed.
by Mike Gabriel 09 Jan '13

09 Jan '13

close #97 thanks This issue has already fixed in one of the last releases. The Win32 build of X2Go Client 4.0.0.1 is still pending. Please use that version, once it is available. Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 1

Bug#97: x2goclient (Windows) needs bash as user's Linux shell
by Markus Kuderer 09 Jan '13

09 Jan '13

Package: x2goclient Version: 3.99.0.0 When connecting from Windows to a x2goserver, this works only when the user's shell is set to "bash" on the Linux server. Setting the shell to (e.g.) "tcsh" will cause the connection to crash with an error message like "Verbindung fehlgeschlagen: log_tclsh.log: Command not found". In case a X2Go server is already started for this user other error messages will occur (depending on the action taken [resume session, new seesion, ...]). Best regards, Markus

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev January 2013