From mikedep333@gmail.com Mon Jan 19 16:06:51 2015 Received: (at 670) by bugs.x2go.org; 19 Jan 2015 15:06:53 +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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 6DFB75DEAB for <670@bugs.x2go.org>; Mon, 19 Jan 2015 16:06:51 +0100 (CET) Received: by mail-we0-f178.google.com with SMTP id p10so31905037wes.9 for <670@bugs.x2go.org>; Mon, 19 Jan 2015 07:06:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=l5Y9h18szPyvAqW07zAqqScS3Up/MoQU4lE2sO6R4Uc=; b=erEfaJzck9lDUqg5Noai8BGfVVnmNn9xAs9bShH40I4QmkboyYwgnQSMguTgSNGXI6 ZjpyCBMGmUkp7nAM6lwaZJdrQO9FT73/mtRHjuFSLG8IQ/0sZiAo5B7tVtmY+aus7x4k Wl7M+uESKetiHNTdZneZMzG4N9ZVkyzPBPDu7WsOnblFvudUJJof5B2Lt6f7nwvhs8R7 lQwHEw21Wx69tnqpMHM47ASY4N48AayPbDavrD4fVivWym3+g7Adz7H0MiQvTJ2Roqdb RaRtWWzQCCHMPR0utNDdoCwKgpPYw1RjO1N4bF91Z+8slcGFUpQdcJedy0EzoWIYYcOl D92g== MIME-Version: 1.0 X-Received: by 10.180.210.167 with SMTP id mv7mr35783354wic.78.1421680011095; Mon, 19 Jan 2015 07:06:51 -0800 (PST) Received: by 10.180.86.132 with HTTP; Mon, 19 Jan 2015 07:06:51 -0800 (PST) In-Reply-To: <20150105102007.Horde.0hAvzZzmpXn3tNc2Gw0vmQ2@mail.das-netzwerkteam.de> References: <20150105102007.Horde.0hAvzZzmpXn3tNc2Gw0vmQ2@mail.das-netzwerkteam.de> Date: Mon, 19 Jan 2015 10:06:51 -0500 Message-ID: Subject: Re: [X2Go-Dev] Bug#670: Bug#670: window border and control disappears after maximize and move From: Michael DePaulo To: Mike Gabriel , x2go.guillaume@zitta.fr, 670@bugs.x2go.org Cc: Alejandro Gallardo Content-Type: text/plain; charset=UTF-8 Sorry for not replying earlier. I need to manage my email better. On Mon, Jan 5, 2015 at 5:20 AM, Mike Gabriel wrote: > @Mike#2: can you provide a diff of the vcxsrv code used in X2Go Client > 4.0.2.1+hotfix1+build6 and in the MS Win X2Go Client version 4.0.3.0? You do not want me to do that. The diff is 38.2 MB. Upstream VcXsrv was upgraded (not updated) from 1.14.3 (19 Sep 2013) to 1.15.2 (5 July 2014). x2goclient 4.0.2.1+* uses https://sourceforge.net/u/mikedep333/vcxsrv/ci/1.14.3.2/ x2goclient 4.0.3.0 uses: https://sourceforge.net/u/mikedep333/vcxsrv/ci/1.15.2.1-xp+vc2013+x2go1/tree/ The only difference I made on top of upstream VcXsrv, other than changing version strings and updating the build process for XP compatibility, was adding Alex's winmultiwindow.patch: https://sourceforge.net/u/mikedep333/vcxsrv/ci/978ec71bbf4345f477fd4f937deb3a4b481862e2/ On Mon, Jan 19, 2015 at 8:23 AM, wrote: > I tested x2go 4.0.3.1 with several version of external VcXsrv (1.15.0.2, > 1.15.1, 1.16.1, 1.16.2) without problem. > (command line option: -multiwindow -notrayicon -clipboard) > > When I switch back to internal X server and problem is back too. Thanks for doing this investigation. It sounds like there are 2 possible causes. 1. The command line options passed to VcXsrv. When you use the internal X server, X2Go Client figures out what options to pass based on your session preferences. So they probably differ than those you listed. 2. Alex's winmultiwindow.patch , which only VcXsrv 1.15.2.1-xp+vc2013+x2go1 & VcXsrv 1.15.2.2-xp+vc2013+x2go1 include. The "+x2go1" in the version string denotes that we made an X2Go-specific change. Specifically, that patch. In order to narrow this problem down, please try the following: 1. Configure x2goclient to use a custom X-server, but specify X2Go Client's own internal X-server as the executable. On 32-bit windows: C:\Program Files\x2goclient\VcXsrv\vcxsrv.exe On 64-bit windows: C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe 2. Specify the same command-line options as before. 3. Restart x2goclient and try to reproduce the bug. -Mike#2