[X2Go-Dev] Bug#627: Baikal?
Hi Mike#2, On Fr 03 Okt 2014 02:35:11 CEST, Michael DePaulo wrote: Hi Mike#1, In X2Go Server baikal (release/4.0.0.x), Trinity is supported and it is affected by this bug. Should I fix this bug in baikal, heuler, and 4.1.0.0? Or only in heuler and 4.1.0.0? I'm thinking that I should investigate how Trinity is launched on various other distros, and then decide. -Mike#2 IMHO, a fix for this bug in Baikal is not required. Mike#1 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpdhNBqRbf7E.pgp Description: Digitale PGP-Signatur ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#626: X2Go issue (in src:x2goserver) has been marked as pending for release
tag #626 pending fixed #626 4.0.1.17 thanks Hello, X2Go issue #626 (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=5231443 The issue will most likely be fixed in src:x2goserver (4.0.1.17). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 52314435eb78a79ea0622450a691a1f672f9d39f Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de Date: Fri Oct 3 12:33:24 2014 +0200 Handle stale X11 socket files in cases where x2goagent has mysteriously disappeared (e.g. kill -9). (Fixes: #626). diff --git a/debian/changelog b/debian/changelog index 882863a..cf332b4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -3,6 +3,8 @@ x2goserver (4.0.1.17-0x2go1) UNRELEASED; 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). -- Mike Gabriel mike.gabr...@das-netzwerkteam.de Thu, 02 Oct 2014 12:18:58 +0200 ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Processed: X2Go issue (in src:x2goserver) has been marked as pending for release
Processing commands for cont...@bugs.x2go.org: tag #626 pending Bug #626 [x2goserver] NX socket cleanup post-session Added tag(s) pending. fixed #626 4.0.1.17 Bug #626 [x2goserver] NX socket cleanup post-session There is no source info for the package 'x2goserver' at version '4.0.1.17' with architecture '' Unable to make a source version for version '4.0.1.17' Marked as fixed in versions 4.0.1.17. thanks Stopping processing here. Please contact me if you need assistance. -- 626: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=626 X2Go Bug Tracking System Contact ow...@bugs.x2go.org with problems ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] [X2Go-Commits] [x2goserver] 01/02: debian/control: Upgrade x2goserver-xsession from Suggests: to Recommends:.
I strongly approve of this change!
Sent from my Android Smartphone
On Oct 3, 2014 10:18 AM, git-ad...@x2go.org wrote:
This is an automated email from the git hooks/post-receive script.
x2go pushed a commit to branch release/4.0.1.x
in repository x2goserver.
commit f5b3c63c983d36e594626f470fdd5229560bfa4f
Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de
Date: Fri Oct 3 15:08:56 2014 +0200
debian/control: Upgrade x2goserver-xsession from Suggests: to
Recommends:.
---
debian/changelog |2 ++
debian/control |2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 67deb50..07afc25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,8 @@ x2goserver (4.0.1.17-0x2go1) UNRELEASED; urgency=medium
mysteriously disappeared (e.g. kill -9). (Fixes: #626).
- Make sure that incompletely started up sessions get wiped from the
session DB after 10 seconds.
+ * debian/control:
++ Upgrade x2goserver-xsession from Suggests: to Recommends:.
-- Mike Gabriel mike.gabr...@das-netzwerkteam.de Thu, 02 Oct 2014
12:18:58 +0200
diff --git a/debian/control b/debian/control
index f531e7f..2fee7cb 100644
--- a/debian/control
+++ b/debian/control
@@ -44,11 +44,11 @@ Recommends:
fontconfig,
xinit,
x2goserver-extensions (= ${source:Version}),
+ x2goserver-xsession (= ${source:Version}),
xfonts-base,
Suggests:
x2goserver-printing (= ${source:Version}),
x2goserver-compat (= ${source:Version}),
- x2goserver-xsession (= ${source:Version}),
x2goserver-fmbindings (= ${source:Version}),
x2goserver-pyhoca (= ${source:Version}),
rdesktop,
--
Alioth's /srv/git/_hooks_/post-receive-email on /srv/git/
code.x2go.org/x2goserver.git
___
x2go-commits mailing list
x2go-comm...@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-commits
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#623: X2Go issue (in src:x2goserver) has been marked as closed
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=6b428c94f421bc5ee21dc40b8507d84172dd7734;hp=ddbb2f0df266094ccdc61bee00e0b955a4e08c4f 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:. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#626: X2Go issue (in src:x2goserver) has been marked as closed
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=6b428c94f421bc5ee21dc40b8507d84172dd7734;hp=ddbb2f0df266094ccdc61bee00e0b955a4e08c4f 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:. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Processed: X2Go issue (in src:x2goserver) has been marked as closed
Processing commands for cont...@bugs.x2go.org: close #626 Bug #626 [x2goserver] NX socket cleanup post-session Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 626: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=626 X2Go Bug Tracking System Contact ow...@bugs.x2go.org with problems ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#628: x2goclient can not be compiled on Raspberry PI
Package: x2goclient Version: 4.0.2.1-0x2go1+git20140823.626+wheezy.main.1 $ uname -a Linux niu5 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux libc6:armhf 2.13-38+rpi2+de gcc 4:4.6.3-8 armhf -- Dear X2go Team, I cannot compile an x2goclient on a Raspberry PI. I just wanted a version of x2goclient that is newer then 3.99.2.1-5. I used the instructions on http://wiki.x2go.org/doku.php/wiki:development:build-howto-linux:x2goclient And then Install x2goclient from git At the end I got the error-msg: g++ -c -O2 -Wall -W -D_REENTRANT -DCFGCLIENT -D__linux__ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I../../x2goclient -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtSvg -I/usr/include/qt4 -I../../x2goclient -I. -I. -I. -o sshmasterconnection.o ../sshmasterconnection.cpp ../sshmasterconnection.cpp: In member function ‘void SshMasterConnection::checkReverseTunnelConnections()’: ../sshmasterconnection.cpp:297:73: error: ‘ssh_channel_accept_forward’ was not declared in this scope ../sshmasterconnection.cpp:308:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] Makefile:710: recipe for target 'sshmasterconnection.o' failed make[1]: *** [sshmasterconnection.o] Error 1 make[1]: Leaving directory '/home/fraroot/scripts/x2goclient/client_build' Makefile:39: recipe for target 'build_client' failed make: *** [build_client] Error 2 I would like to download x2goclient package ready for the Raspberry PI. But when I say # apt-get download x2goclient I get x2goclient_3.99.2.1-5_armhf.deb And this version makes a lot of problems with an X2goserver 4.0.1.16. If you have a version of x2goclient with 4.x.x for the Raspberry PI that would make me happy. Attached you find the detailed messages. Thank you very much and have a nice day, Franz Lückl Mobil DE: +49 152 3437 5620 Mobil AT: +43 676 37 00 299 Mobiles Festnetz: +49 69 3487 8985 Fax: +43 1 89 00 2999 mailto:fr...@nextitlevel.de Internet Home Page: http://www.nextitlevel.de Cloning into 'x2goclient'... remote: Counting objects: 5354, done. remote: Compressing objects: 100% (4526/4526), done. remote: Total 5354 (delta 3903), reused 948 (delta 631) Receiving objects: 100% (5354/5354), 18.32 MiB | 669 KiB/s, done. Resolving deltas: 100% (3903/3903), done. lrelease-qt4 x2goclient.pro Project MESSAGE: if you want to build x2goplugin you should export X2GO_CLIENT_TARGET=pluginProject MESSAGE: building x2goclient x2goplugin with ldap and cupsUpdating '/home/fraroot/scripts/x2goclient/x2goclient_de.qm'... Generated 566 translation(s) (566 finished and 0 unfinished) Updating '/home/fraroot/scripts/x2goclient/x2goclient_da.qm'... Generated 536 translation(s) (526 finished and 10 unfinished) Ignored 30 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_es.qm'... Generated 554 translation(s) (543 finished and 11 unfinished) Ignored 12 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_et.qm'... Generated 566 translation(s) (566 finished and 0 unfinished) Updating '/home/fraroot/scripts/x2goclient/x2goclient_fi.qm'... Generated 566 translation(s) (566 finished and 0 unfinished) Updating '/home/fraroot/scripts/x2goclient/x2goclient_fr.qm'... Generated 254 translation(s) (201 finished and 53 unfinished) Ignored 312 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_nb_no.qm'... Generated 537 translation(s) (524 finished and 13 unfinished) Ignored 29 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_nl.qm'... Generated 566 translation(s) (566 finished and 0 unfinished) Updating '/home/fraroot/scripts/x2goclient/x2goclient_pt.qm'... Generated 0 translation(s) (0 finished and 0 unfinished) Ignored 566 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_ru.qm'... Generated 552 translation(s) (543 finished and 9 unfinished) Ignored 14 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_sv.qm'... Generated 537 translation(s) (523 finished and 14 unfinished) Ignored 29 untranslated source text(s) Updating '/home/fraroot/scripts/x2goclient/x2goclient_zh_tw.qm'... Generated 397 translation(s) (372 finished and 25 unfinished) Ignored 169 untranslated source text(s) mkdir -p /home/fraroot/scripts/x2goclient/client_build cd /home/fraroot/scripts/x2goclient/client_build qmake-qt4 QMAKE_CFLAGS= QMAKE_CXXFLAGS= QMAKE_LFLAGS=-lldap -lcups -lX11 -lXpm ../x2goclient.pro Project MESSAGE: if you want to build x2goplugin you should export X2GO_CLIENT_TARGET=plugin Project MESSAGE: building x2goclient with ldap and cups cd
[X2Go-Dev] Bug#626: NX agent dies not reliably remove socket files under /tmp/.X11-unix
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
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Processed (with 1 errors): Re: Bug#626: NX agent dies not reliably remove socket files under /tmp/.X11-unix
Processing control commands:
clone -1 -2 -3
Bug #626 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de} [x2goserver]
NX socket cleanup post-session
Bug 626 cloned as bugs 630-631
reopen -2 -3
Failed to reopen 630: New submitter address '-3' is not a valid e-mail address.
retitle -2 clean up stable /tmp/.Xdisp-lock files
Bug #630 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de} [x2goserver]
NX socket cleanup post-session
Changed Bug title to 'clean up stable /tmp/.Xdisp-lock files' from 'NX socket
cleanup post-session'
retitle -3 develop X2Go Server session manager
Bug #631 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de} [x2goserver]
NX socket cleanup post-session
Changed Bug title to 'develop X2Go Server session manager' from 'NX socket
cleanup post-session'
severity -2 important
Bug #630 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de} [x2goserver]
clean up stable /tmp/.Xdisp-lock files
Severity set to 'important' from 'wishlist'
severity -3 wishlist
Bug #631 {Done: Mike Gabriel mike.gabr...@das-netzwerkteam.de} [x2goserver]
develop X2Go Server session manager
Ignoring request to change severity of Bug 631 to the same value.
--
626: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=626
630: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=630
631: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=631
X2Go Bug Tracking System
Contact ow...@bugs.x2go.org with problems
___
x2go-dev mailing list
x2go-dev@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#629: Display port conflicts: Client access to multiple servers
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? ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
