X2Go Bug report logs - #656
Fwd: Windows X2GoClient hangs when launching x2gostartagent

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#656: [X2Go-Dev] Bug#656: Fwd: Windows X2GoClient hangs when launching x2gostartagent
Reply-To: Kyle Cottongim <cottonke@gmail.com>, 656@bugs.x2go.org
Resent-From: Kyle Cottongim <cottonke@gmail.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Wed, 29 Oct 2014 13:35:02 +0000
Resent-Message-ID: <handler.656.B656.141458947820947@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 656
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 656-submit@bugs.x2go.org id=B656.141458947820947
          (code B ref 656); Wed, 29 Oct 2014 13:35:02 +0000
Received: (at 656) by bugs.x2go.org; 29 Oct 2014 13:31:18 +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,
	HTML_MESSAGE,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id F244F5DB48;
	Wed, 29 Oct 2014 14:31:15 +0100 (CET)
Received: by mail-yh0-f44.google.com with SMTP id f10so563364yha.3
        for <multiple recipients>; Wed, 29 Oct 2014 06:31:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=cdywIevuRyckt6leiTBBwDMm2y6yNZs5hiYJhj/r1AY=;
        b=hXIKskblHqbOnALxLOEouy2lx2uNSAJAjfzszk65TzQ0HS8VgNvSMVIanT7inD5aQu
         VHTK8SlvOH01XZ8hvr0LU+FWpsilJIRl4dI5gkUYgwCylaRxgKcmfzgTG5wRcgrWCf6v
         AiBk6NR5SwA29dpquAZluWo4ydJqTIl9N80az7v5BCwW4Fan82hbF1Z2/8rEPQ2imTov
         HwswngiNSUEcx5zCMVH6xCQ6BP/sovsTMNmfruhs577MNpa/p7dmxKPgxeq7Pz4bWK/F
         QHZ6ttDF/4RTjYUX2stx5DtF4D8YUK0CnMXOEGmJMiOplwrIv1LkSVwUCne8xks9LQoj
         VXqw==
X-Received: by 10.170.220.8 with SMTP id m8mr11220169ykf.48.1414589474704;
 Wed, 29 Oct 2014 06:31:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.187.145 with HTTP; Wed, 29 Oct 2014 06:30:54 -0700 (PDT)
In-Reply-To: <20141029093932.Horde.QzW4YecVJXaLTQxWF36nrQ1@mail.das-netzwerkteam.de>
References: <CAPxkJXKdd89R=TdjaZtrgr2ZDpE4WABG96gXyf3PdCaBfi3PNg@mail.gmail.com>
 <CAPxkJXL=z6kBJy4PdM4yypTjqPs42aqmki9OHkYHqxxBw5XGNA@mail.gmail.com> <20141029093932.Horde.QzW4YecVJXaLTQxWF36nrQ1@mail.das-netzwerkteam.de>
From: Kyle Cottongim <cottonke@gmail.com>
Date: Wed, 29 Oct 2014 08:30:54 -0500
Message-ID: <CAPxkJXJ3Y1G2+PQt5KN9BE6QQCNw7zXqR7r4YEJSMP-wGqF7Ag@mail.gmail.com>
To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Cc: 656@bugs.x2go.org, submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary=001a11390932249c6405068fc7dc

[Message part 1 (text/plain, inline)]

Hello Mike,

On Wed, Oct 29, 2014 at 4:39 AM, Mike Gabriel <
mike.gabriel@das-netzwerkteam.de> wrote:

> Hi Kyle,
>
> On  So 26 Okt 2014 00:04:16 CEST, Kyle Cottongim wrote:
>
>  Package: X2GoClient
>> Version: 4.0.3.0
>>
>> When launching a session from within the X2GoClient, the process will hang
>> after the following call:
>>
>> x2go-DEBUG-onmainwindow.cpp:3900> Executing remote command:
>> "x2gostartagent
>> 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME both"
>>
>> This does not happen all the time, but generally happens after loss of
>> network connection or after logging out instead of just closing the
>> X2GoClient window. A complete restart of the client machine will solve the
>> issue.
>>
>
> Could you cross-check the debug output of X2Go Server, possibly add some
> more log message to /usr/bin/x2gostartagent, so that we can narrow down,
> where the "hang" actually occurs?
>
> Does x2gostartagent get executed at all, or is X2Go Client aready stalling
> before executing that command.
>
> Or is x2gostartagent hanging somewhere on the way? (Extra log messages
> placed in x2gostartagent will be helpful then).
>
> Regards,
> Mike


​During this launch attempt, it seems the client is getting a bit further
along than before, but still not to the point of launching something​. Here
is how far things are getting now:

x2go-DEBUG-onmainwindow.cpp:2778> SSH connection established.
x2go-DEBUG-onmainwindow.cpp:3038> Continue normal x2go session
x2go-DEBUG-onmainwindow.cpp:3382> ""
x2go-DEBUG-onmainwindow.cpp:3769> Fullscreen: false
x2go-DEBUG-onmainwindow.cpp:9257> got localhost
x2go-DEBUG-onmainwindow.cpp:9279> Port is free: 6000
x2go-DEBUG-onmainwindow.cpp:9345> using internal X: true
x2go-DEBUG-onmainwindow.cpp:9368> WxH:"1440"x"900"
x2go-DEBUG-onmainwindow.cpp:9373> "-multiwindow -notrayicon -clipboard"
x2go-DEBUG-onmainwindow.cpp:9410> Running "C:/Program Files
(x86)/x2goclient\vcxsrv\vcxsrv.exe" "-multiwindow -notrayicon -clipboard :0"
x2go-DEBUG-onmainwindow.cpp:3900> Executing remote command: "x2gostartagent
1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME both"
x2go-DEBUG-onmainwindow.cpp:9257> got localhost
x2go-DEBUG-onmainwindow.cpp:9285> Port already used: 6000
x2go-DEBUG-onmainwindow.cpp:9439> X is started.
x2go-DEBUG-onmainwindow.cpp:9790> All winservers are started.

With some debug within the x2gostartagent I can tell that it is executing
this script and now seems to be getting past this point. I have turned the
logging level of the server to debug and here is the output I am seeing
during a connection attempt:

Oct 29 08:02:33 oddjob /usr/bin/x2golistsessions[12799]: x2golistsessions
has been called with no option
Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: x2gostartagent called with
options: 1440x900 adsl 16m-jpeg-9 unix-kde-depth_32 us pc105/us 1 D GNOME
both
Oct 29 08:02:34 oddjob /usr/bin/x2gostartagent: client announced itself as
,,131.199.103.76''
Oct 29 08:02:34 oddjob /usr/bin/x2gosessionlimit[12835]: x2gosessionlimit
has been called
Oct 29 08:02:34 oddjob /usr/bin/x2golistsessions[12838]: x2golistsessions
has been called with options: --all-servers

I added some more debug messages to x2golistsessions and am seeing that
this script seems to finish execution (I reach deubg statements just before
closing syslog).

Another note is that even after restart of the client and server PCs, this
is not working. Also, If I keep my client open for a long time after it
"hangs", it will sometimes eventually bring up the remote session. The time
it takes for it to do this is on the order of magnitude of many hours.

Thanks,
Kyle

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.