From mikedep333@gmail.com  Sun Jun 28 02:54:08 2015
Received: (at 891) by bugs.x2go.org; 28 Jun 2015 00:54:11 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
	T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com [209.85.160.177])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 7E9165DA84
	for <891@bugs.x2go.org>; Sun, 28 Jun 2015 02:54:08 +0200 (CEST)
Received: by ykdy1 with SMTP id y1so88322204ykd.2
        for <891@bugs.x2go.org>; Sat, 27 Jun 2015 17:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=kPjEOxM4KPXPwHMP5IWZ1EX+RCxvq5V1Ub7clfqP5+k=;
        b=eFKsilqNlYl+8ciaEZSRwzm7vuIiKy/3s0nI+RWyH38Q5VoV5BlaeWy2IKOKlZfdqF
         jCV5w7zEofNal7t21qCiB6DpKvOABJOETIZBroY1qk/As0ey78sdizP+mFs97uRwgPnq
         RxZsb8x3mgVOwf4K2J147VieOGF0qv6xqf6kEXNJpkhv1OeddHnuDXXTh55z1w81rP12
         L9YPqoa96sLac7ntaLd+hDRky08lrzJeJoZRVluo+a8ecWlopaEY7lOvACrEjshaYnCW
         re7Ue7qQ4fKXUwedQH3RPgGn1qLVRH3Wf5XUn/Dz4WHKRBcmv3PngsFj+t65P15mT5sj
         OpgQ==
MIME-Version: 1.0
X-Received: by 10.170.205.212 with SMTP id w203mr10731765yke.55.1435452847163;
 Sat, 27 Jun 2015 17:54:07 -0700 (PDT)
Received: by 10.37.214.10 with HTTP; Sat, 27 Jun 2015 17:54:07 -0700 (PDT)
Date: Sat, 27 Jun 2015 20:54:07 -0400
Message-ID: <CAMKht8gEghD6LXLHBovhRdrDW9vmAzaoONHn+wmW=2z4BB+_Bw@mail.gmail.com>
Subject: I have a fix for VcXsrv, but it needs discussion
From: Michael DePaulo <mikedep333@gmail.com>
To: 891@bugs.x2go.org
Content-Type: text/plain; charset=UTF-8

So here is the fix for VcXsrv (which is bundled with X2Go Client) that
I ported from Cygwin XWin:
https://github.com/ArcticaProject/vcxsrv/commit/d45db884b19a0f081fcd259e3b338a13378c936d

Here is a test build of VcXsrv :
https://github.com/ArcticaProject/vcxsrv/releases/tag/1.17.0.0-2-bug4test1
(I do not make a test build of X2Go Client available yet, so you'll
have to test it via the "X.Org Server settings" GUI in X2Go Client.)

And here is the issue against VcXsrv (X2Go/Arctica Builds):
https://github.com/ArcticaProject/vcxsrv/issues/4

Read that issue for more details on why this bug happens with X2Go
(and its component nx-libs.) Discussion over the details of the patch
should be discussed there (or in a PR.)

However, If I release X2Go Client 4.0.4.1 (or an update to 4.0.4.0)
with this fix, then sessions started on X2Go Client for Windows
4.0.4.0-2015.06.24 and earlier can not be resumed on the new version.
This could be very disruptive to users.

Does anyone have any thoughts on this dilemma?

-Mike#2