Hi Mike,
are you still there? We like X2Go very much - great work! Is there any chance to solve this problem in Vcxsrv? Or maybe give a possible reason for the problem, so that the ROOT programmers could think about a solution. I know it is a relatively small user group using ROOT together with X2Go Client for Windows, but I would be very glad to get it working without installing an old Vcxsrv version.
Kind regards, Patrick
Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos!
Am 26.01.2017 um 11:34 schrieb prinz.charles@freenet.de:
Hi Mike,
are you still there? We like X2Go very much - great work! Is there any chance to solve this problem in Vcxsrv? Or maybe give a possible reason for the problem, so that the ROOT programmers could think about a solution. I know it is a relatively small user group using ROOT together with X2Go Client for Windows, but I would be very glad to get it working without installing an old Vcxsrv version.
Well, I'm not Mike#2, but you might want to check if the crash isn't actually caused server-side by the old NX-libs.
If you can set up a test system (please don't try this on a production system, especially if you don't have a backup!), try following the steps listed here: http://wiki.x2go.org/doku.php/doc:howto:nx-libs-betatesting
After that, try connecting with X2GoClient 4.0.5.2 (and the VcXsrv we ship with it) and see what happens.
If you're still experiencing the problem, please wait a few weeks until around 2017-02-09, when X2GoClient 4.1.0.0 is scheduled to be released and try again.
->Still no change? Then please let us know.
-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
Okay, so last night, I had a chance to try this myself. Upgrading NX-Libs does not help. It is indeed more likely to be a client-side issue, rather than a case of the NX-Libs sending garbage that then kills the client.
When starting the "root" application on a "stable" (Debian Jessie/Stable and X2Go stable) system, "root" complains at startup that it is missing a font named adobe-helvetica-<something>, and it hints at package names that may include this font. The closest matches to those package names are already installed, though. Seems to me that it's looking for client-side fonts, rather than server-side fonts.
Running "TBrowser b" insider "root" causes the crash.
Upgrading to X2Go heuler + Arctica Nightlies does not change a single bit.
However, using the latest stock VcXsrv build (<https://netcologne.dl.sourceforge.net/project/vcxsrv/vcxsrv/1.18.3.0/vcxsrv.1.18.3.0.installer.exe>), rather than the X2Go/Arctica one fixes the issue - plus the complaint regarding the missing font goes away.
I tried this by selecting the use of a custom X.org server in X2GoClient's settings menu, pointing it at the vcxsrv.exe of the newly installed package, and restarting X2GoClient (this is important) before attempting to connect.
Next, I tried to find out if it might simply be a font issue. So I copied the content of the fonts folder from the newer VcXsrv installation to the one shipped with X2GoClient, set X2GoClient so it would use its own VcXsrv copy again, and restarted the client. Sadly, this causes it to crash again when repeating the steps from above
- so it is not a case of missing fonts (alone).
-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
-
prinz.charles＠freenet.de -
Stefan Baur