x2go-dev

x2go-dev@lists.x2go.org

5399 discussions

Bug#632: X2Go issue (in src:x2goserver) has been marked as pending for release
by Mike Gabriel 08 Oct '14

08 Oct '14

tag #632 pending fixed #632 4.0.1.19 thanks Hello, X2Go issue #632 (src:x2goserver) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=33a64a3 The issue will most likely be fixed in src:x2goserver (4.0.1.19). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 33a64a3e7b94d04d1e72de2a81db04b86432c7c5 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Wed Oct 8 05:26:30 2014 +0200 Prevent bash failures when sourcing external bash scripts beyond our scope. (Fixes: #632). diff --git a/debian/changelog b/debian/changelog index 95865b5..58d0ced 100644 --- a/debian/changelog +++ b/debian/changelog @@ -6,6 +6,8 @@ x2goserver (4.0.1.19-0x2go1) UNRELEASED; urgency=medium - Be a bit more tolerant when trying to detect if a desktop icon is to be removed (using regexp, not eq). + - Prevent bash failures when sourcing external bash scripts + beyond our scope. (Fixes: #632). * debian/control: + Add D (x2goserver): libfile-which-perl. * x2goserver.spec:

2 1

Bug#630: X2Go issue (in src:x2goserver) has been marked as closed
by Mike Gabriel 08 Oct '14

08 Oct '14

close #630 thanks Hello, we are very hopeful that X2Go issue #630 reported by you has been resolved in the new release (4.0.1.18) of the X2Go source project »src:x2goserver«. You can view the complete changelog entry of src:x2goserver (4.0.1.18) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver. http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=8af2d72466b1ea3… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2goserver Version: 4.0.1.18-0x2go1 Status: RELEASE Date: Mon, 06 Oct 2014 22:27:42 +0200 Fixes: 630 Changes: x2goserver (4.0.1.18-0x2go1) RELEASED; urgency=medium . [ Horst Schirmeier ] * New upstream release (4.0.1.18): - Remove stale X11 lock files in cases where x2goagent mysteriously disappeared (e.g., due to kill -9 or a crash). (Fixes: #630).

3 5

Bug#632: x2goserver Xsession fix for Gentoo (and probably RHEL)
by Mike Gabriel 08 Oct '14

08 Oct '14

Package: x2goserver-xsession Version: 4.0.1.18 the below bug report reached my private mail address. Quoting it here nonetheless. A fix is on its way... For bug description in English see [1]. Mike [1] https://bugs.gentoo.org/show_bug.cgi?id=524350 ----- Weitergeleitete Nachricht von "Dr. Bernd Feige" <Bernd.Feige(a)gmx.net> ----- Datum: Tue, 07 Oct 2014 21:31:31 +0200 Von: "Dr. Bernd Feige" <Bernd.Feige(a)gmx.net> Betreff: x2goserver Xsession fix An: mike.gabriel(a)das-netzwerkteam.de Hallo Mike, könntet Ihr Euch mal den Bug https://bugs.gentoo.org/show_bug.cgi?id=524350 anschauen? Ein simpler Patch liegt bei (set +e / set -e um die Ausführung der Dateien in /etc/X11/xinit/xinitrc.d/). Wenn Ihr das bislang nicht gesehen haben solltet - es hat bei mir zuvor auch so funktioniert, aber neuerdings hat gdm eine Datei 49-keychain dort installiert, dessen "which keychain" bei mir nichts findet. Ohne set +e hat das einen Abbruch zufolge. Danke und herzliche Grüsse, Bernd ----- Ende der weitergeleiteten Nachricht ----- -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby 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

Bug#630: X2Go issue (in src:x2goserver) has been marked as pending for release
by Mike Gabriel 06 Oct '14

06 Oct '14

tag #630 pending fixed #630 4.0.1.18 thanks Hello, X2Go issue #630 (src:x2goserver) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=0174a52 The issue will most likely be fixed in src:x2goserver (4.0.1.18). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 0174a5202742636f020f01df0c9c04f95980bdbb Author: Horst Schirmeier <horst(a)schirmeier.com> Date: Mon Oct 6 22:17:25 2014 +0200 Remove stale X11 lock files in cases where x2goagent mysteriously disappeared (e.g., due to kill -9 or a crash). (Fixes: #630). diff --git a/debian/changelog b/debian/changelog index 64683f4..3504855 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,6 +1,9 @@ x2goserver (4.0.1.18-0x2go1) UNRELEASED; urgency=medium - * Continue development... + [ Horst Schirmeier ] + * New upstream release (4.0.1.18): + - Remove stale X11 lock files in cases where x2goagent mysteriously + disappeared (e.g., due to kill -9 or a crash). (Fixes: #630). -- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Mon, 06 Oct 2014 22:13:22 +0200

2 1

DebConf 2015
by Stefan Baur 06 Oct '14

06 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, DebConf 2015 will take place in Heidelberg, Germany, between 2015-08-15 and 2015-08-22. This isn't *that* far away from where Heinz, Alex and I are located. I wonder if we should try to get involved, and if so, how? - -Stefan - -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUMlKAAAoJEG7d9BjNvlEZ3JQH/ArB4hVlmXjZzrM3Gsq46VNO NZbqa39RfE9XCJhil3u2J7LdxxQvC2ve9K0D1MZwRA5WOZ+6OvPk67OUAiLvxXlB pRoV4ZSCwqrcX2JsdDWJALRJdIeu42fFgxACgMHVhrkSuqhKeSFP7+aNxJj1cejt KYRBEgp0GpxhsVuTTmwk5mwGoNdY58RCzeFHNHuMRtYIk8n542r4nD4s8EHUOONM H1dO9fZzWy75Xvl1D6uk/zuxx57/Mn3KIUIKCsXmPKiKFsHkpRAQDRslY68FrHPR yGYuFTkv6Flg6jxZUlfTO/gFvsQX1Fjx6nBU6xr/DswvPAVHFnbkI9v4YvRiRlM= =0B0U -----END PGP SIGNATURE-----

1 0

Bug#630: [PATCH] Handle stale X11 lock files (Fixes: #630)
by Horst Schirmeier 05 Oct '14

05 Oct '14

Remove stale X11 lock files in cases where x2goagent mysteriously disappeared (e.g., due to kill -9 or a crash). This fixes bug #630 (and #626, which hasn't really been fixed yet). Tested against the original scenario from bug #626. --- x2goserver/sbin/x2gocleansessions | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/x2goserver/sbin/x2gocleansessions b/x2goserver/sbin/x2gocleansessions index eb1bd3f..3b3775b 100755 --- a/x2goserver/sbin/x2gocleansessions +++ b/x2goserver/sbin/x2gocleansessions @@ -171,6 +171,11 @@ elsif ($pid == 0 ) syslog('warning', "@sinfo[1], pid @sinfo[0] cleaning up stale X11 socket file: /tmp/.X11-unix/X$display"); unlink("/tmp/.X11-unix/X$display"); } + if (-e "/tmp/.X$display-lock") { + # remove the NX-X11 lock file (as the agent will not have managed after a kill -9) + syslog('warning', "@sinfo[1], pid @sinfo[0] cleaning up stale X11 lock file: /tmp/.X$display-lock"); + unlink("/tmp/.X$display-lock"); + } syslog('debug', "@sinfo[1]: unmounting all shares"); system( "su", "@sinfo[11]", "-c", "export HOSTNAME && x2goumount-session @sinfo[1]"); } @@ -184,6 +189,12 @@ elsif ($pid == 0 ) syslog('warning', "@sinfo[1], pid @sinfo[0] cleaning up stale X11 socket file: /tmp/.X11-unix/X$display"); unlink("/tmp/.X11-unix/X$display"); } + if (-e "/tmp/.X$display-lock") { + # remove the NX-X11 lock file (we don't know how the agent disappeared, + # someone might have shot it with kill -9) + syslog('warning', "@sinfo[1], pid @sinfo[0] cleaning up stale X11 lock file: /tmp/.X$display-lock"); + unlink("/tmp/.X$display-lock"); + } syslog('debug', "@sinfo[1], pid @sinfo[0] does not exist, changing status from @sinfo[4] to F"); syslog('debug', "@sinfo[1]: unmounting all shares"); system("su", "@sinfo[11]", "-c", "export HOSTNAME && x2goumount-session @sinfo[1]"); -- 2.0.0.5.gbce14aa -- PGP-Key 0xD40E0E7A

3 2

Bug#626: NX agent dies not reliably remove socket files under /tmp/.X11-unix
by Horst Schirmeier 03 Oct '14

03 Oct '14

OK, to summarize the scenario: - A normal user connects, gets the first display :50, runs his session. /tmp/.X50-lock and /tmp/.X11-unix/X50 are owned by this user. - The user decides to killall -u username -9. (Don't ask. The actual story was that the logout process didn't complete, and he tried to clean up behind him, having accustomed to use kill -9 all the time.) - This kicks the user's nxagent out of business (the same would happen if it simply crashes), which prevents it from cleaning up the sockets in /tmp. - Another user connects, and also gets assigned the first display (because, for some reason, x2go is convinced it's free again). His x2go processes are not permitted to remove and recreate /tmp/.X50-lock and /tmp/.X11-unix/X50, and the window manager dies immediately. All users besides the initial user are locked out of x2go from now on. Manual workaround: Remove stale /tmp/.X??-lock and /tmp/.X11-unix/X??. Apply LART to users of kill -9 against nxagent. Automatic workaround: x2gocleansessions should probably take care of the /tmp file removal. LART will still need to be applied manually. A "real" fix would move the usual, immediate cleanup step out of the user's control. This could, for example, happen by a daemon running as root, that spawns a nxagent at a user's request, under the user's UID. Once the nxagent dies (from whatever cause), the daemon's SIGCHLD handler does the cleanup. This would also remove the race condition (up to 2s delay before the sockets are cleaned up; connection of new users may be impossible in this time window) introduced by the aforementioned "automatic workaround". Another, much simpler possibility would be to use randomized/uniqe socket names instead of the fixed /tmp/.X${DISPLAYNUM}-lock / /tmp/.X11-unix/X${DISPLAYNUM} scheme. But I don't know enough about X11 to judge whether this could work. -- Horst -- PGP-Key 0xD40E0E7A

2 1

Bug#629: Display port conflicts: Client access to multiple servers
by Jerry Rabe 03 Oct '14

03 Oct '14

Package: x2goserver Version: 4.0.1.15 Server OS: Centos 6.5 x86_64 Server X2go Version: 4.0.1.15 (installed from source) Client OS & version: Windows 7 Professional, Version 6.1 (Build 7601 Service Pack 1) Client X2go Version: x2goclient-4.0.2.1+hotfix1+build4-fullfonts When using a single client machine to connect to two x2goserver machines with two simultaneous x2goclient processes, the second client session corrupts the first one because they both connect to the client using Display port 50. The first x2gosession is unresponsive and must be killed manually. Shouldn't x2goclient break with a warning about conflicting ports? Is there a way to configure each x2goserver to connect with a different range of ports? (i.e. the same as when configuring each Freenx server with a unique DISPLAY_BASE variable in /etc/nxserver/node.conf) In addition, once the x2gosession is corrupted on the first machine, then even after reboots, any new x2gosessions start up OK, but if they are resumed, both server & client log files say it resumes, but the x2go window never appears on the client's screen. Does something need to be cleared in the server's database?

1 0

Bug#626: X2Go issue (in src:x2goserver) has been marked as closed
by Mike Gabriel 03 Oct '14

03 Oct '14

close #626 thanks Hello, we are very hopeful that X2Go issue #626 reported by you has been resolved in the new release (4.0.1.17) of the X2Go source project »src:x2goserver«. You can view the complete changelog entry of src:x2goserver (4.0.1.17) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver. http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=6b428c94f421bc5… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2goserver Version: 4.0.1.17-0x2go1 Status: RELEASE Date: Fri, 03 Oct 2014 17:09:23 +0200 Fixes: 623 626 Changes: x2goserver (4.0.1.17-0x2go1) RELEASED; urgency=medium . * New upstream release (4.0.1.17): - Fix breakage of X2Go Server when upgrading from 4.0.1.15 while sessions are still in running / suspended state. (Fixes: #623). - Handle stale X11 socket files in cases where x2goagent has mysteriously disappeared (e.g. kill -9). (Fixes: #626). - Make sure that incompletely started up sessions get wiped from the session DB after 10 seconds. - Fix unreliable removal of client-side folder sharing desktop icons. - Update date in several man pages. * debian/control: + Upgrade x2goserver-xsession from Suggests: to Recommends:.

2 1

Bug#623: X2Go issue (in src:x2goserver) has been marked as closed
by Mike Gabriel 03 Oct '14

03 Oct '14

close #623 thanks Hello, we are very hopeful that X2Go issue #623 reported by you has been resolved in the new release (4.0.1.17) of the X2Go source project »src:x2goserver«. You can view the complete changelog entry of src:x2goserver (4.0.1.17) below, and you can use the following link to view all the code changes between this and the last release of src:x2goserver. http://code.x2go.org/gitweb?p=x2goserver.git;a=commitdiff;h=6b428c94f421bc5… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2goserver. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2goserver Version: 4.0.1.17-0x2go1 Status: RELEASE Date: Fri, 03 Oct 2014 17:09:23 +0200 Fixes: 623 626 Changes: x2goserver (4.0.1.17-0x2go1) RELEASED; urgency=medium . * New upstream release (4.0.1.17): - Fix breakage of X2Go Server when upgrading from 4.0.1.15 while sessions are still in running / suspended state. (Fixes: #623). - Handle stale X11 socket files in cases where x2goagent has mysteriously disappeared (e.g. kill -9). (Fixes: #626). - Make sure that incompletely started up sessions get wiped from the session DB after 10 seconds. - Fix unreliable removal of client-side folder sharing desktop icons. - Update date in several man pages. * debian/control: + Upgrade x2goserver-xsession from Suggests: to Recommends:.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev