Am 09.04.20 um 10:31 schrieb Stefan Baur:
This looks like the default status log from X2GoClient's info window. We might get a more detailed (and thus, potentially more helpful) error log out of it if your colleague installs the debug version of X2GoClient (that's a checkbox during install), then opens cmd.exe and runs x2goclient like so (after changing into the directory where the X2Go executables reside, most likely "C:\Program Files (x86)\x2goclient\"):
x2goclient.debug.exe --debug >%TEMP%\x2godebug.txt 2>&1
After that, the file %TEMP%\x2godebug.txt should contain the debug log, which you should forward to 1455@bugs.x2go.org after anonymizing/pseudonymizing any confidential information (like user account names, IP addresses and the like).
Ah, stupid me. If your colleague is trying to run X2GoClient inside WSL, then that particular version of X2GoClient already has debug functionality built in.
So inside the WSL environment, the command to create a debug log would be something like
x2goclient --debug >/tmp/x2godebug.txt 2>&1
Kind Regards, Stefan Baur
-- 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