From unknown Sat May 16 08:17:18 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1474: Same problem on CentOS 8 with Xfce session Reply-To: Rob Whalley , 1474@bugs.x2go.org Resent-From: Rob Whalley Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Sat, 27 Jun 2020 14:20:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1474 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: References: Received: via spool by 1474-submit@bugs.x2go.org id=B1474.15932674836549 (code B ref 1474); Sat, 27 Jun 2020 14:20:02 +0000 Received: (at 1474) by bugs.x2go.org; 27 Jun 2020 14:18:03 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,HTML_MESSAGE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 5569A5DAC1 for <1474@bugs.x2go.org>; Sat, 27 Jun 2020 16:17:58 +0200 (CEST) Received: from thor.home ([86.189.55.27]) by mrelayeu.kundenserver.de (mreue009 [213.165.67.99]) with ESMTPSA (Nemesis) id 1M26iv-1jr7Sm2i9x-002aLJ for <1474@bugs.x2go.org>; Sat, 27 Jun 2020 16:17:57 +0200 Message-ID: From: Rob Whalley To: 1474@bugs.x2go.org Date: Sat, 27 Jun 2020 15:17:56 +0100 In-Reply-To: Content-Type: multipart/alternative; boundary="=-Xhi8Vjrw3/oJ6f8KG1P8" User-Agent: Evolution 3.36.3 (3.36.3-1.fc32) MIME-Version: 1.0 X-Provags-ID: V03:K1:rStIJ293kReYWCK6eEpduaERDRHJBRhvPO9200vyxLf1S5ID9pc U5o6YN6hOlI8xQ6G6OR3gKqJtWApyrzn3D7yBSfznCMrMU+ygqBHBDowFRMq7dU3+HeeT9H pmrhgylBp8Rx0QADBvFJP+8w7UJEk822WgS2GaHFvno0kyCBlKuCe9FRZcNUydt9SIHliDu XZdL5+VDdDS+cgxGW9AxQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:RLEfC1j/AMM=:3mLMzNWbl+kOrzTsl8xM7O zNejftf1qXedJKRswCGKh2e5KxwP0Dk3hDWP+AFIu1/0swaBkBYUlCBKKwxY0hsuiQsSnHJqL /va8Z8/oTCyedqHYhcsmcSMi0O3th1SX5f7R8TfCLwjfLn8MCQDpeaN3CxQEcz/Dskdiy5l1E 4vZxedPqZJ24s83rbcC2D3S4mWD7OZcYXt/G+xpDkyOVva9hochK2A1Q2V6vofOrznBIfvXjl 41kGZ5LN2pc6/sjA28aMXBbsiG8zy+btWWLKVV26UBbjAY/ZyNSfI63xNwgtghONe3RSgRf6o o/y7jAN8xnpMnmIPVqw26+mwUXXTMtaGbS6cBQJ39O8osiI/2Ce/Z8JDzr3Ba2rHSegOKx4ml fw2DjQ+/94kl3lEE54q2HnzurXx+4EtLBqbA6ZggLZpzZJ8FzRIQBKchRBps+oFvRU1ut+A3g jVvjxkmwSkZptZjaRV05SupoFATxb04ebzJR3TH9J6DGO0hUEaHjxrNQLsfSUyGMeEMZIciRu tT2GHyC56RuUVZr32hLcczNvFHYa6sHTrjcfWu/pyX4K+u5AZ7woKdsSVRJ2/yx6j3AnLVAHd TqdvXIR6ZevsoOvDO5BfLglcMPb3i/8T86uZucHRALxR6Ra3aRaCFQQMwyfzKMbNod1ZdAfRq ixWmb5XlIEzlViyp9L+99zYLgszvKlMNfhsVSyVvzOJJglDaFvbdMsteW6N4MW31DDzDAl963 70fzuGtzJPZTd44UOst9XNcrOxwaP8NoHIHREwZrIJ7JDnFvF5/b25AjYQtTN6GgdCl66LLUj msrjnZZBrR6obipbDlV30H2WVtTegF1BY2/4MuCc7+SV0Jm1GSL9W0E9BmCuwlpW9ESor6F --=-Xhi8Vjrw3/oJ6f8KG1P8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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" 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 --=-Xhi8Vjrw3/oJ6f8KG1P8 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
I had the same issue connecting to a Centos 8 server running Xfce.= Clearly the connection was still responding, as screen elements would resi= ze with the window but mouse and keyboard input would appear unresponsive.<= /div>
Suspecting the screensaver, I had previously tried disabling all = screensaver / screen blanking / power options in Xfce I could find, but thi= s did not seem to help.
Manually testing the screensaver from the= options worked fine.

I tried Pavel's workaround o= f killing the xfce4-screensaver process and that seemed to work (thank= you Pavel!).

When checking the list of running pr= ocesses I did notice that both gsd-screensaver-proxy and xfce4-screens= aver 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 n= o screensaver at all:

1. Disable the gnome screens= aver:
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.
<= br>
I suspect it relates to X2go not supporting Mutter, and gsd-s= creensaver-proxy trying to start it up, but it would need a developer to co= mment really.

Thanks and kind regards,
R= ob


On Wed, 3 Jun 2020 07:48:38 +0000 "Pa= vel Duda - pavel.duda@cz.ibm.com" <pavel.duda@cz.ibm.com&= gt; 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, th= e
> keyboard and mouse is "locked" of course. My  workaround so far i= s to
> kill xfce-screensaver completely to resume control over session.
>
> Pavel
--=-Xhi8Vjrw3/oJ6f8KG1P8--