X2Go Bug report logs - #204
Error starting an aborted session

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#204: Error starting an aborted session
Reply-To: Dick Kniep <dick@lindix.nl>, 204@bugs.x2go.org
Resent-From: Dick Kniep <dick@lindix.nl>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: owner@bugs.x2go.org
X-Loop: owner@bugs.x2go.org
Resent-Date: Wed, 08 May 2013 09:48:02 +0000
Resent-Message-ID: <handler.204.B.136800609330860@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: report 204
X-X2Go-PR-Package: x2go-agent
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.136800609330860
          (code B); Wed, 08 May 2013 09:48:02 +0000
Received: (at submit) by bugs.x2go.org; 8 May 2013 09:41:33 +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=MIME_QP_LONG_LINE,
	URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail.lindix.nl (mail.lindix.nl [95.170.66.31])
	by ymir (Postfix) with ESMTP id 05E905DB18
	for <submit@bugs.x2go.org>; Wed,  8 May 2013 11:41:33 +0200 (CEST)
Received: from mail.int.lindix.nl (localhost [127.0.0.1])
	by mail.lindix.nl (Postfix) with ESMTP id BB4263FE1E
	for <submit@bugs.x2go.org>; Wed,  8 May 2013 11:41:32 +0200 (CEST)
From: Dick Kniep <dick@lindix.nl>
To: submit@bugs.x2go.org <submit@bugs.x2go.org>
Date: Wed, 8 May 2013 11:41:32 +0200
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-Mailer: Zarafa 7.0.8-35178
Message-Id: <zarafa.518a1dcc.4c2f.77d2dbd7163e8492@mail.int.lindix.nl>

package: x2go-agent
Severity: severe
Version: 0.4.0.1

If a session is aborted because of a network problem, x2goagent does not end properly. Sometimes it does, most of the time it doesn't We are working with a ssh-proxy, maybe there is a cause. 

Included is the log on the server for the user. As you can see at a certain moment it says "nxagentBlockHandler: No application running. Closing the session." I don't know what causes this, it might be a segmentation fault in the application. However, it gets worse, because after this, it is impossible for the user to login again. The only way to end the session is by kill -9. After that the user can login again.......

NXAGENT - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '32154'.
Session: Starting session at 'Wed May  8 08:29:51 2013'.
Info: Proxy running in server mode with pid '32154'.
Info: Waiting for connection from 'localhost' on port '30001'.
Info: Accepted connection from '127.0.0.1'.
Info: Connection with remote proxy completed.
Info: Using ADSL link parameters 512/24/1/0.
Info: Using agent parameters 5000/10/50/0/0.
Info: Using cache parameters 4/4096KB/8192KB/8192KB.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_17'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 4/4.
Info: No suitable cache file found.
Info: Listening to X11 connections on display ':50'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
Info: Using alpha channel in render extension.
Info: Not using local device configuration changes.
keyboard file created
SessionPath not defined
Session: Session started at 'Wed May  8 08:29:58 2013'.
I/O warning : failed to load external entity "/etc/nx/keystroke.cfg"
nxagentBlockHandler: No application running. Closing the session.
Session: Terminating session at 'Wed May  8 08:32:57 2013'.
Info: Waiting the cleanup timeout to complete.
Session: Session terminated at 'Wed May  8 08:32:58 2013'.





Met vriendelijke groet,
Dick Kniep
Lindix BV
tel. 036-5215580
mob. 06-50991858

Send a report that this bug log contains spam.