X2Go Bug report logs - #583
Windows client closes session when inactive

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Pavel Hanák <hanak@is-it.eu>

Date: Tue, 26 Aug 2014 13:50:01 UTC

Severity: normal

Found in version 4.2.0.1+hotfix1+build3

Done: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Bug is archived. No further changes may be made.

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#583: [X2Go-Dev] Bug#583: Yes, it is probably vxcsrc.exe crash
Reply-To: Michael DePaulo <mikedep333@gmail.com>, 583@bugs.x2go.org
Resent-From: Michael DePaulo <mikedep333@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: Tue, 16 Sep 2014 04:25:01 +0000
Resent-Message-ID: <handler.583.B583.141084142319975@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 583
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 583-submit@bugs.x2go.org id=B583.141084142319975
          (code B ref 583); Tue, 16 Sep 2014 04:25:01 +0000
Received: (at 583) by bugs.x2go.org; 16 Sep 2014 04:23:43 +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.0 required=5.0 tests=BAYES_40,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham version=3.3.2
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 853E35DB54
	for <583@bugs.x2go.org>; Tue, 16 Sep 2014 06:23:41 +0200 (CEST)
Received: by mail-wg0-f50.google.com with SMTP id x13so4808159wgg.33
        for <583@bugs.x2go.org>; Mon, 15 Sep 2014 21:23:41 -0700 (PDT)
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=VXTQIQYF/BJ13DndCDxg+3pHpK+HBS4NU6532jcbpas=;
        b=Pqg5zjFZR8h2rrpoa+SCuxIYmFHTgKwMAr4L8I5cPLgv+LFVwf8vnWxxJOag28XkBc
         ExedS+s89ALtz2PN3cZN1fZvc7Xs6Ka8wKKRdLs3ckyf4AzfO8V+CDa9UIHFrd7pW9NV
         Eosg4cooqv8yLOO/lqwsKJvykcI+4KuElPCBcXcqQBJgwGH6fGEkul+5JVQQ67vZmbSu
         lQDJxq3jEu45bQ+EsNXkeULIZUUa9ZxpSBFNsYLRJCyuyoKFoVgtbEsSybML8n2S7Bfx
         EIxBINetEiK3pyHQfmlTgoX1MyYbrdqbDFtdcT6FkYGpFl9fh7ASlOUFNnTgD4Z37oQd
         N/OA==
MIME-Version: 1.0
X-Received: by 10.180.188.13 with SMTP id fw13mr13108422wic.83.1410841421210;
 Mon, 15 Sep 2014 21:23:41 -0700 (PDT)
Received: by 10.180.106.39 with HTTP; Mon, 15 Sep 2014 21:23:41 -0700 (PDT)
In-Reply-To: <83r3zc7kp9.fsf@alfik.amazon.xx>
References: <83r3zc7kp9.fsf@alfik.amazon.xx>
Date: Tue, 16 Sep 2014 00:23:41 -0400
Message-ID: <CAMKht8gKvL1xU-hFKUknGH5srV0CUD-LDYbhi3H_UkyAGAdcow@mail.gmail.com>
From: Michael DePaulo <mikedep333@gmail.com>
To: 583@bugs.x2go.org
Cc: Hanak <hanak@is-it.eu>
Content-Type: text/plain; charset=UTF-8
Hi Hanak,

On Mon, Sep 15, 2014 at 3:22 PM, Hanak <hanak@is-it.eu> wrote:
> You are probably right that this is vxcsrv.exe crash.
I don't think it is a vcxsrv.exe crash. Probably a bug in nxproxy
(running on the client) or nxagent (running on the server.) nxproxy
interacts with VcXsrv, so minimizing VcXsrv could trigger an nxproxy
bug.

> Could I switch on some debugging in order to see what is happening?
You can enable debug output for the client by installing the debug
build, and then launching x2goclient.exe with the --debug argument.
This will cause log info to be outputted to stdout/stderr.
This is the current released debug build:
http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.1+hotfix1+build4/non-default-builds/x2goclient-4.0.2.1+hotfix1+build4-debug-setup.exe
I recommend launching xgoclient.exe with "--debug" from the command
prompt. This will make it easier for you to copy and paste the output
to a file/email.
Also, right click on the command prompt title bar, select
"properties", and increase the "screen buffer size" width to like 400.

For the server, edit /etc/x2go/x2goserver.conf and set:
loglevel=debug

IIRC, in addition to causing more output to be logged to syslog, it
will also cause the per-session log files to be kept, rather than
deleted at the end of the session. For example, on my server, there is
the symlink:
/home/mike/.x2go/C-mike-319-1410831069_stDGNOME_dp32/session.log
which points to:
/tmp/.x2go-mike/session-C-mike-319-1410831069_stDGNOME_dp32.log

-Mike#2

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Sun Dec 8 13:32:03 2019; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.