X2Go Bug report logs - #1117
x2goclient "stuck session" for select users that cannot be resumed or terminated

Full log

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

Received: (at 1117) by bugs.x2go.org; 29 Nov 2016 12:02:39 +0000
From X2Go-ML-1@baur-itcs.de  Tue Nov 29 13:02:38 2016
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.8 required=3.0 tests=BAYES_50 autolearn=ham
	version=3.3.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id DC37D3BC8A
	for <1117@bugs.x2go.org>; Tue, 29 Nov 2016 13:02:37 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uJyNbUDLSBfA for <1117@bugs.x2go.org>;
	Tue, 29 Nov 2016 13:02:27 +0100 (CET)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 7287C3BC7D
	for <1117@bugs.x2go.org>; Tue, 29 Nov 2016 13:02:27 +0100 (CET)
Received: from [192.168.0.171] ([78.43.90.159]) by mrelayeu.kundenserver.de
 (mreue003 [212.227.15.129]) with ESMTPSA (Nemesis) id
 0M5c8C-1cvy6Y1QAC-00xcId for <1117@bugs.x2go.org>; Tue, 29 Nov 2016 12:57:26
 +0100
Subject: Re: [X2Go-Dev] Bug#1117: x2goclient "stuck session" for select users
 that cannot be resumed or terminated
To: 1117@bugs.x2go.org
References: <7FB7E7E5-D686-423F-B1C2-D5D6982A4E2C@queensu.ca>
From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
Message-ID: <95cc01bd-9ab2-8205-31b9-684c49fc6b9f@baur-itcs.de>
Date: Tue, 29 Nov 2016 12:57:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <7FB7E7E5-D686-423F-B1C2-D5D6982A4E2C@queensu.ca>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="lsjn8mk1u8HEEKMfK8uEK7CVVNbPu7gmH"
X-Provags-ID: V03:K0:WCXv2+oyKNUGNz+8lYhWTfKC76roL9Jyh6d1LU9Jf5ZUjE+sAMX
 zPZjQc7UzEglPAbxq7y9TIDFi4SiiYunaTjWVM2ig87cJ47j4c6uutLtLLBC7MhvRGtYdDT
 7Jv3qu8s831nNGlCIbLP5YvIBp0pdbc7utRZWP2r5kPnOJpBZUoSdLwNPhyzX+36wCml+oZ
 rVUXgD4VkmSsHxkgu9I6A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:8swegseNE50=:s/6fMUO+lzrHD8bV7bPuI7
 bR5IGf8WKCfsnEqseGYZa3aj2dhzVVn7TBlSqxJudJsQGA+cDNqjluQ6UoYAYLjgbUUMfiGOt
 3nAHG9CO7JflqnltMCox2vbKXW9svHISOCdvNsZX1gRaTmlnG05d/IZ2AQg5cO/FknPl37xYY
 zjMnJGxS2yAdyy1iqL7M6SQFPLg+eHMquoAH37XMM0Ls/NUxTbahH5NGNR/NzktR6+HMl1+bK
 LxvElaP+TjP2Nmua3NUMUlo1a3R7IFmpGFWmZMMafU3CjVmDur2rK0tbIXyIVFvXzg+Ab8C9X
 w0NW8HsDW//cY4zRDLyGZ6DTM4oM8WLnA/AHayRR4d905rHJorc35Ne1b13cSk4GuwRXf7SXM
 hlVQwb3GJM7WeCBGdDpHtDuq/LmppZUlgtXoN1+doyfO6DoEuD29OygVLwX9t7S7ONmbFiNPz
 +ZWqymkxWYeP0kvOpRvHkME7wvsDCzJUb/1MCOEUHZa1Qc1ihPVGoBOIKJh12wfH+igo3Uqzp
 Rcc0YjxySIP9EY4m3w2jQ0ivvGKu82nRx2kVRCSzopBRGOV+wT118KF+B3TlnvmMPkGUsdrXs
 derRvq4rp4w+awToRRpTspAIQx7zbQ+0qovoqntfiC9dHYcxlSm3L1mFypZZ0lr2qLXfNZJQh
 OeXFbxO3AkcsCfQIjq0CFQsWUYUf6287ggLcugJC5r/O2yHuU4iYfqKh65/XDWOZ67QM=

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

Am 28.11.2016 um 23:31 schrieb Jordan Poppenk:
> Package: x2goclient (mac)
> Version: 4.0.5.2
>
> Above is my best guess as to the affected package, although I am not certain it is on the client end. Also, my issue is similar to the one reported here:
> http://lists.x2go.org/pipermail/x2go-dev/2015-October/010734.html
> ...but that thread concludes without a solution that works for me.
>
> x2go had been working for a dozen users of my server. One day, two of the users reported that they were no longer able to log in -- they were kicked back to the login screen after entering their ssh private key encryption password. After entering this, the users get the result: 
> - Session: Session session started at: (date)
> - Warning: Protocol mismatch or no X authentication data.
> - Session: Terminating session at (date)
> - Info: Your session was closed before reaching a usable state.
> - Info: This can be due to the local X server refusing access to the client.
> - Info: Please check authorization provided by the remote X application.
> - Session: Session terminated at (date)
> Sometimes, they are presented with a list of sessions that shows their "running" session. It allows them to terminate the session, then brings them back to the screen where they would terminate the session.
>
> It is worth noting that their configuration was previously working. Also, I am sometimes able to fix issues like this by deleting the user's .Xauthority files, their .x2go folder, and their cache/lxsession folder; and rebooting. In this case, none of these things influenced the outcome of their login attempts. But, many other users are still able to access x2go normally on the same machine.

What happens when you, as root, execute:

x2golistsessions_root

Do you see the "hung" sessions of your users?

What happens when you terminate them using

(again, as root, and preferably not in an X2Go session yourself)

x2goterminate-session <sessionid>

(<sessionid> is what you see in the second output column of
x2golistsessions_root)

Does it work for them afterwards?

What happens when you set up a separate test server with X2Go on it, can
they connect to that one, or are they having issues with it as well?


> Jordan Poppenk, Ph.D.
> Canada Research Chair in Cognitive Neuroimaging
> Department of Psychology and Centre for Neuroscience Studies
> Queen's University
> http://popmem.com
> 613-533-6009

There are two things I would like to mention, due to your e-mail signature:

First, a warning:
X2Go does have options for image compression, like using JPG and/or PNG.
Not all image compression algorithms are lossless, and thus there may be
artifacts in the images (i.e. the image displayed through X2Go may look
slightly different than what it would look like on a regular X-Server
screen), depending on which algorithm and which compression level you
choose. Is that something you're aware of?

If you're using fMRI/X-Ray/Mammography/... images displayed through X2Go
for clinical purposes (deciding whether a certain patient requires a
surgery etc.), you should absolutely make sure that you're using a
lossless compression or no compression at all, or else you might be
seeing things that aren't actually there, or missing things that are there.

Second, a shameless plug advertising our commercial services:
<shameless plug>
X2Go also has a commercial side, where various companies - including my
own - offer support contracts with guaranteed response times as well as
consultancy and paid-for development work if someone wants to see a bug
fixed or a new feature added in a certain time frame. What makes my
company special is, IMHO:

1) I'm the current X2Go Project/Community Coordinator, so the
development lead and the developers tend to listen to me.
2) As far as I know, we are the only company providing X2Go support that
isn't a one-man-show.
3) We sub-contract other developers from the X2Go community on demand,
so you only have one person you need to talk to - me - and you will only
receive one invoice, even if the task involved several freelance or
part-time X2Go developers.

Our hourly rate for consultancy work and fixing issues outside of a
support contract is 110 EUR. With a support contract, you get guaranteed
response times (starting at 400 EUR/month for 24h response time during
business hours in the CET/CEST time zone from Monday to Friday, German
holidays excluded) and lower hourly rates if you buy a certain amount of
hours in advance.
</shameless plug>

Kind Regards,
Stefan Baur

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.