X2Go Bug report logs - #77
X2Go Client corrupts Cygwin

Full log

Message #15 received at submit@bugs.x2go.org (full text, mbox, reply):

Received: (at submit) by bugs.x2go.org; 6 Dec 2012 11:29:26 +0000
From newsgroups.mail2@stefanbaur.de  Thu Dec  6 12:29:26 2012
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8])
	by ymir (Postfix) with ESMTP id 34EEC3BC43;
	Thu,  6 Dec 2012 12:29:26 +0100 (CET)
Received: from [192.168.2.3] (dslb-188-105-115-187.pools.arcor-ip.net [188.105.115.187])
	by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis)
	id 0LvkQW-1T6GuT3AC4-017R5D; Thu, 06 Dec 2012 12:29:22 +0100
Message-ID: <50C081A3.3040909@stefanbaur.de>
Date: Thu, 06 Dec 2012 12:29:39 +0100
From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 77@bugs.x2go.org, 
 x2go-dev@lists.berlios.de
CC: submit@bugs.x2go.org, Anders.Hallstrom@delaval.com
Subject: Re: [X2Go-Dev] Bug#77: Fwd: Bug report, unknown package: X2Go corrupts
 CygWin
References: <20121206095821.23244ju0rz4iytyl@mail.das-netzwerkteam.de>
In-Reply-To: <20121206095821.23244ju0rz4iytyl@mail.das-netzwerkteam.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V02:K0:BvNVGNWSV99Cs/GDaGCz8GA5TginX6fIb/3gxuyfzAj
 +idaCg5FpOlMPc/9I131atZlCIomoj0lISdYzyPEsZAb1nmX1n
 WdkAs38UqBGlvuHPJOHcfjazDmmli9Pm9LkuVZDftx2z1rO/17
 8tzVFxkbhxebfI9ImxF7cDpvHUTww5Xe4jOCn1HllBRwfFGmzQ
 04kxtXaAMcvvk2iDfnP+7xi2t0C1ttz38cbhEx9fHXzi2enkpg
 /PXMOSzj46uwsWeOwUfSmg+SNiC2ZbhFio5Do0Y9lIIfjKap1N
 itp5HVtmPmTOsm7mUrQELXJdjjUhuMbLGzEyzSnySuXrql846q
 2U2CeaRIux2ObUDqnmDANeh5Vo0JlCuIhncytukFJ

Am 06.12.2012 09:58, schrieb Anders Hallström:
[...]

> What happens is that directories from the X2Go installation are
> suddenly mounted as /etc and /bin in CygWin.
> Since fundamental commands such as "/bin/ls" are thereby missing,
> nothing works.

[...]

> After this fix, I can still use X2Go without problems and without
> the mounts coming back, so I just cannot see why the mounts were
> necessary in the first place.
>
> Sometimes, however, the harmful mounts do come back.
> I cannot pinpoint exactly when this happens,
> but at least it is not every time I restart the computer and not every
> time I run X2Go.
>
> Is this known?
> Could some developer explain what is happening?

Well, X2Go uses some Cygwin code for its Windows client.
I've seen weird things happen before when two applications brought their 
own set of Cygwin libraries and they belonged to different versions, 
maybe this is a similar issue.
Probably something like whoever loads cygwin1.dll first "wins", the 
other application is blocked from loading its own version of cygwin1.dll 
and just has to make do with whatever cygwin1.dll is already in memory. 
 After that, it's either an application from the old Cygwin failing 
because the newer cygwin1.dll is doing something unexpected, or it's a 
new application failing because the old cygwin1.dll doesn't offer the 
function that it is expecting.

So, to debug this issue, it would be interesting to see what happens 
when you first run X2GoClient and keep it in the background, then try to 
rund your old Cygwin applications, and what happens when you run your 
old applications first (keeping at least one window of them open) and 
start X2GoClient afterwards.
Also, be aware that it is wrong to assume that all X2Go tasks have been 
terminated just because you don't see an X2Go icon in your task bar. 
Running task manager after closing X2GoClient, you may still encounter a 
running pulseaudio, sshd and/or vcxsrv on your Windows client.
If you see these, terminete them from within task manager before running 
your old cygwin applications and see if that helps.
I'm not suggesting that this is the solution to your problem, but I am 
sure the results will be helpful for the devs to pinpoint the issue.

-Stefan

Send a report that this bug log contains spam.