X2Go Bug report logs - #100
X2GoClient locks up if connection with server gets disrupted

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

Reported by: Christoph Mathys <eraserix@gmail.com>

Date: Tue, 15 Jan 2013 16:48:01 UTC

Severity: grave

Tags: confirmed, pending

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: git-admin@x2go.org
Subject: Bug#100: 
Reply-To: Stefan Baur <newsgroups.mail2@stefanbaur.de>, 100@bugs.x2go.org
Resent-From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: git-admin@x2go.org
Resent-Date: Tue, 15 Jan 2013 21:18:02 +0000
Resent-Message-ID: <handler.100.B100.135828381323732@bugs.x2go.org>
Resent-Sender: git-admin@x2go.org
X-X2Go-PR-Message: followup 100
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 100-submit@bugs.x2go.org id=B100.135828381323732
          (code B ref 100); Tue, 15 Jan 2013 21:18:02 +0000
Received: (at 100) by bugs.x2go.org; 15 Jan 2013 21:03:33 +0000
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10])
	by ymir (Postfix) with ESMTP id DA0B55DB0D;
	Tue, 15 Jan 2013 22:03:32 +0100 (CET)
Received: from [192.168.0.3] (HSI-KBW-149-172-200-27.hsi13.kabel-badenwuerttemberg.de [149.172.200.27])
	by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis)
	id 0Lsrle-1SyDFu1cgk-012bbw; Tue, 15 Jan 2013 22:03:32 +0100
Message-ID: <50F5C448.9040004@stefanbaur.de>
Date: Tue, 15 Jan 2013 22:04:08 +0100
From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: 100@bugs.x2go.org, x2go-dev@lists.berlios.de
CC: submit@bugs.x2go.org
References: <CALqGcGpL2Pr0dAxa+=yGpTJgY-Sc7ejTVuk=Fkqx1Hi4NcSe5Q@mail.gmail.com>
In-Reply-To: <CALqGcGpL2Pr0dAxa+=yGpTJgY-Sc7ejTVuk=Fkqx1Hi4NcSe5Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:thtPqKmNaS1m61EcOz9QUl/Sq2LZTyanYo6tcFpIcEJ
 pLCZxxPnjtT5Z760D3TNlj0ftsvA+gFFSZlWN+Vm8MhWkRE29J
 TJ5tbsKfiBXRyJCBhy8DFcFBL8gYrzNnUZEwKCKmQQNHj5F+Hz
 MC1WZOG8P+639gLEf7s5h6w5UPF/pR+iAC38CjVtD0qrjJMzT1
 oH7sRJJ2rHD8/7HyptYlK5lSrKdl2HMkfa8EBWg+rGtXn0aIFS
 xj3SQWTcNMFAHqUOGlLONHlNUFANnsubZp/Vrl9qdO9Wbiet4o
 Tq1FPA1zp/6UrcvVRGk6o/PRS99QeiFXqkLb+dSp0zzN0F+pvL
 PEbtipeCOC9amsLbUVB5mzmumzQNYE+UxMl1tRWOR
Am 15.01.2013 17:36, schrieb Christoph Mathys:

> The x2go-client seems to deadlock if I do a reboot/shutdown of the server.

<snip>

I can confirm this for 3.99.3.0 (with old PulseAudio), MS Windows 7.
Earlier versions are also affected, though I haven't tried them all to 
check if the bug was introduced somewhere along the road or has been in 
there from the very beginning.

The same error also occurs when network connectivity is lost or the 
client-side screensaver activates (not immediately, though - it seems to 
take a few minutes before it locks up).

Deadlock in this case means unresponsiveness *and* very high CPU load by 
the x2goclient.exe task (the "idle" task is at 0% and x2goclient at up 
to 99%).

-Stefan

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Apr 18 23:48:39 2024; 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.