X2Go Bug report logs - #1474
keyboard and mouse stop working after a few minutes of inactivity

version graph

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

Reported by: "K. Kirsa" <dex@gmx.org>

Date: Sun, 24 May 2020 08:15:01 UTC

Severity: normal

Found in version 4.1.0.3-5

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1474; Package x2goserver. (Sun, 24 May 2020 08:15:01 GMT) (full text, mbox, link).


Acknowledgement sent to "K. Kirsa" <dex@gmx.org>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sun, 24 May 2020 08:15:01 GMT) (full text, mbox, link).


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

From: "K. Kirsa" <dex@gmx.org>
To: submit@bugs.x2go.org
Subject: keyboard and mouse stop working after a few minutes of inactivity
Date: Sun, 24 May 2020 10:14:22 +0200
Package: x2goserver
Version: 4.1.0.3-5

Ubuntu server 20.04 lts with xubuntu-desktop, installed on actual hardware, not a vm. No physical keyboard or mouse connected.

After a while of inactivitiy (neither keyboard nor mouse are being used for a few minutes), the keyboard and mouse controls are lost. The session itself does not freeze: Windows with constantly updating contents or panel plugins still work. Resizing the x2go client window correctly resizes the remote xfce desktop. It's just like the keyboard and mouse are being disconnected somehow.

It does not matter, if the x2go client (ms windows) stays connected or if I disnonnect and reconnect the client after a few minutes to resume the session: Keyboard and mouse even get lost during my "absence". The problem seems to be independent of the client. A new session suffers the same fate after a few minutes of inactivity.

I disabled the screensaver and session locking in xfce settings. There's nothing I'm aware of happening in xfce that could act as a trigger for the keyborad and mouse loss. I searched the logs but did not manage to find any errors.

Any ideas on where to look or what to try next?

BTW: The same machine works perfectly fine with 18.04 lts, xubuntu-desktop and x2goserver.


Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1474; Package x2goserver. (Wed, 03 Jun 2020 07:50:02 GMT) (full text, mbox, link).


Acknowledgement sent to "Pavel Duda - pavel.duda@cz.ibm.com" <pavel.duda@cz.ibm.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Wed, 03 Jun 2020 07:50:02 GMT) (full text, mbox, link).


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

From: "Pavel Duda - pavel.duda@cz.ibm.com" <pavel.duda@cz.ibm.com>
To: "1474@bugs.x2go.org" <1474@bugs.x2go.org>
Subject: Same problem on Fedora32 with Xfce session
Date: Wed, 3 Jun 2020 07:47:43 +0000
I have found that the issue seems to be the screen saver. Looks like
screen saver starts up but doesn't show anything on the screen (does
not blank the screen) so user still see the workspace, the keyboard and
mouse is "locked" of course. My  workaround (so far) is to kill xfce-
screensaver completely to resume control over session.

Pavel

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1474; Package x2goserver. (Wed, 03 Jun 2020 07:50:02 GMT) (full text, mbox, link).


Acknowledgement sent to "Pavel Duda - pavel.duda@cz.ibm.com" <pavel.duda@cz.ibm.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Wed, 03 Jun 2020 07:50:02 GMT) (full text, mbox, link).


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

From: "Pavel Duda - pavel.duda@cz.ibm.com" <pavel.duda@cz.ibm.com>
To: "1474@bugs.x2go.org" <1474@bugs.x2go.org>
Subject: Same problem on Fedora32 with Xfce session
Date: Wed, 3 Jun 2020 07:48:38 +0000
I have found that the issue seems to be the screen saver. Looks like
screen saver starts up but doesn't show anything on the screen (does
not blank the screen or starts the so user still see the workspace, the
keyboard and mouse is "locked" of course. My  workaround so far is to
kill xfce-screensaver completely to resume control over session.

Pavel

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1474; Package x2goserver. (Sat, 27 Jun 2020 14:20:02 GMT) (full text, mbox, link).


Acknowledgement sent to Rob Whalley <mail@robwhalley.co.uk>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sat, 27 Jun 2020 14:20:02 GMT) (full text, mbox, link).


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

From: Rob Whalley <mail@robwhalley.co.uk>
To: 1474@bugs.x2go.org
Subject: Same problem on CentOS 8 with Xfce session
Date: Sat, 27 Jun 2020 15:17:56 +0100
[Message part 1 (text/plain, inline)]
I had the same issue connecting to a Centos 8 server running Xfce.
Clearly the connection was still responding, as screen elements would
resize with the window but mouse and keyboard input would appear
unresponsive.Suspecting the screensaver, I had previously tried
disabling all screensaver / screen blanking / power options in Xfce I
could find, but this did not seem to help.Manually testing the
screensaver from the options worked fine.
I tried Pavel's workaround of killing the xfce4-screensaver process and
that seemed to work (thank you Pavel!).
When checking the list of running processes I did notice that both gsd-
screensaver-proxy and xfce4-screensaver were running (makes sense as
Centos 8 comes with Gnome 3 installed by default, although it does not
work with X2Go, hence why I installed Xfce in the first place!). While
killing the xfce4-screensaver process does work, I believe the solution
below will work permanently, at the cost of seeing no screensaver at
all:
1. Disable the gnome screensaver:gsettings get
org.gnome.desktop.screensaver idle-activation-enabled
2. Kill the gsd-screensaver-proxy process - normally it will
automatically spawn a new process if you kill it, if it does not re-
spawn then the change above has worked.
It is to be noted that even if you have the Xfce screensaver activated,
power options switched on, etc. the screensaver will not appear at all
once the above has been done, at least in the simple testing I did.
I suspect it relates to X2go not supporting Mutter, and gsd-
screensaver-proxy trying to start it up, but it would need a developer
to comment really.
Thanks and kind regards,Rob

On Wed, 3 Jun 2020 07:48:38 +0000 "Pavel Duda - pavel.duda@cz.ibm.com"
<pavel.duda@cz.ibm.com> wrote:

> I have found that the issue seems to be the screen saver. Looks like

> screen saver starts up but doesn't show anything on the screen (does

> not blank the screen or starts the so user still see the workspace,
the

> keyboard and mouse is "locked" of course. My  workaround so far is to

> kill xfce-screensaver completely to resume control over session.

> 

> Pavel



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

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Tue Aug 4 03:24:36 2020; 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.