Subject: Bug#723: Current theory: It's a regression in VcXsrv that can be worked around without needing an out-of-date client or VcXsrv version

From: Stefan Baur <[email-masked]>
Date: Mon, 30 Jan 2017 15:43:42 +0100

Debugging this with the help of Mike#2 turned up the following:

If you select an external X-Server in X2GoClient's settings, yet point
it back at the VcXsrv that is shipped with X2GoClient, it will work,
provided:

- the options for the various X-Server modes default to this:
	-screen 0 %wx%h -notrayicon -clipboard
	-fullscreen -notrayicon -clipboard
	-multiwindow -notrayicon -clipboard
	-nodecoration -notrayicon -clipboard -screen 0 @
- you restarted X2GoClient after making these changes
- you run a full desktop environment in windowed mode
  (it still crashes in single application/published application mode)

The "-screen 0 800x600 -notrayicon -clipboard :0" entry is the most
relevant one.

Note that these settings may have unwanted side effects if you are using
X2GoClient to connect in different modes.

Especially, this *will* break Published Application Mode.  Single
Application Mode is unaffected, but running the problematic app this bug
is about will still cause a crash in Single Application Mode.

-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