Package: x2goclient Version: 4.0.3.0
x2goserver-version: 4.0.1.18-0~949 running on Ubuntu 14.04.1 x2goclient-version: 4.0.3.0 running on Windows 7
We are experiencing a strange bug in the interplay of x2go with a component of the ROOT data analysis framework (https://root.cern.ch). Displaying GUI windows in the ROOT framework, shows them shortly and results in an immediate CRASH of the X2go connection with a Windows error "vcxsrv.exe has stopped working" and subsequent closure of all opened remote applications. Strangely the GUI window shows up when resuming the session in X2go. Running the ROOT GUI window from pure vcxsrv, Xming, Mobaxfire or similar Windows X-Server applications works flawlessly. It also worked previously with the "baikal" version of X2go. I admit this seems to be an exotic bug but there might be further graphical software affected which increases the severity of this bug.
Steps to reproduce:
After this the x2goclient slowly fills the "session" log with warnings of "Proxy: WARNING! Handling data for finishing FD#6 channel ID#1."
This bug is a kind of a show stopper for us because we need ROOT for scientific use. I would help to further track down the error and debug if I can get some hints where and how to start.
Kind regards, Martin
Hi Martin,
On Mi 07 Jan 2015 19:33:42 CET, Babutzka, Martin (EKP) wrote:
Package: x2goclient Version: 4.0.3.0
x2goserver-version: 4.0.1.18-0~949 running on Ubuntu 14.04.1 x2goclient-version: 4.0.3.0 running on Windows 7
We are experiencing a strange bug in the interplay of x2go with a
component of the ROOT data analysis framework
(https://root.cern.ch). Displaying GUI windows in the ROOT
framework, shows them shortly and results in an immediate CRASH of
the X2go connection with a Windows error "vcxsrv.exe has stopped
working" and subsequent closure of all opened remote applications. Strangely the GUI window shows up when resuming the session in X2go.
Running the ROOT GUI window from pure vcxsrv, Xming, Mobaxfire or
similar Windows X-Server applications works flawlessly. It also
worked previously with the "baikal" version of X2go. I admit this
seems to be an exotic bug but there might be further graphical
software affected which increases the severity of this bug.Steps to reproduce:
- Install ROOT from the webpage or via "apt-get install
root-system-bin" on the x2goserver- Run "root" on command line.
- Open a TBrowser with the command "TBrowser b"
After this the x2goclient slowly fills the "session" log with warnings of "Proxy: WARNING! Handling data for finishing FD#6 channel ID#1."
This bug is a kind of a show stopper for us because we need ROOT for
scientific use. I would help to further track down the error and
debug if I can get some hints where and how to start.Kind regards, Martin
Is it possible to be granted access to a reference installation that
shows the above describe behaviour?
Esp. the fact, that resuming the "crashed" session gives me a bit of
hope here.
Also: do you know if your software uses the X11 bigrequests extension?
Thanks+Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby 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...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 08.01.2015 um 10:52 schrieb Mike Gabriel:
[Remote X application instantly crashes]
Is it possible to be granted access to a reference installation that shows the above describe behaviour?
Esp. the fact, that resuming the "crashed" session gives me a bit of hope here.
Also: do you know if your software uses the X11 bigrequests extension?
I've seen the exact same behavior, also with a Windows client, when I was running an older X2GoClient release and trying to run Chrome/Chromium. It would "zap" the session whenever certain menu items were clicked, x2goclient.exe/vcxsrv.exe would terminate with exactly the same error, and resuming the session after restarting all X2GoClient components (VcXSrv, PulseAudio, SSH) allowed one to continue - until the next crash.
For me, switching to a newer client version that brought a newer VcXSrv helped, so maybe the issue is similar here. Of course, 4.0.3.0 is almost the newest version we have ... so maybe it would be worth a try with another X-Server, like the one from mingw maybe?
I guess Mike#2 could offer some suggestions/advice here, CCing him so he takes notice.
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)
iQEcBAEBAgAGBQJUrlnOAAoJEG7d9BjNvlEZlqAIAJawOG2cPy/llvoR+nWw4Srl e5jAjMA4viOdaDZP6IHCZCXKsaIUi+zGcshiPiFiFlPtxBXjqGSxCMzCFwjZOuVO EGGoa4wehuGhvuSFYkHfBSTbgWTPcRnc/MSHL8iJ4QceJvDTEN7DZ9AwLwdkkllV D6rVOp+TcoeBoW+2/kmo5UTTcMQOt2QukXFRylugbN8TirFP+yf4jcqR/jmS/JA8 Sp+mq5GznItRFBwWrBe31sMZ8w5J4S+fAd3ASflxdNbqt/YxxSZaTvzt8W1x29m3 LYSTjQWd0ReTL6/ruOAWXK9TESpwHD9UHaC9nnz7xfK7sIP1LrtnJ1IJSmVoy+g= =LLKa -----END PGP SIGNATURE-----