Re: [X2Go-User] Losing mouse click ability and keyboard events
Le 01/10/2020 à 13:02, Stefan Baur a écrit : Am 30.09.20 um 14:19 schrieb Nicolas Ecarnot: Hello, The day after, I can testify that changing the power-saving settings on the server prevented this issue to rise again. I don't know if it's worth writing that somewhere in a FAQ but for the record, I wanted to write it here at least. Well, for that, it would be nice to know which power-saving settings you changed. Do you still remember them? If you only know their French names, that's still better than nothing, I'm sure we can figure them out somehow. Kind Regards, Stefan Baur I agree with Ulrich about the fact that it IS strange that the mouse movements are still working, so these mouse inputs are took into account, but the clicks are not. About the power-saving settings, this is simple, in my Xubuntu, I guess the control panel is the same as in every *ubuntu variants, at least when it's about power-saving settings. I disabled *every* power-saving setup, making Greta Thunberg cry. But at least, this server is a VM, doing very little. To stay serious, I'm running out of idea about how to add more logs, read more docs, and detect at which point this issue is appearing. -- Nicolas Ecarnot ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Losing mouse click ability and keyboard events
Am 30.09.20 um 14:19 schrieb Nicolas Ecarnot: > Hello, > > The day after, I can testify that changing the power-saving settings on > the server prevented this issue to rise again. > I don't know if it's worth writing that somewhere in a FAQ but for the > record, I wanted to write it here at least. Well, for that, it would be nice to know which power-saving settings you changed. Do you still remember them? If you only know their French names, that's still better than nothing, I'm sure we can figure them out somehow. 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 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Losing mouse click ability and keyboard events
On Wed, Sep 30, 2020 at 2:20 PM Nicolas Ecarnot wrote: > > Hello, > > The day after, I can testify that changing the power-saving settings on > the server prevented this issue to rise again. Nice hearing that ist works for you, but I cannot really believe that. Why? Because you can still move the mouse and hover over elements, so input IS working. How could power-saving settings influence only the mouse clicks and keyboard but not the rest!? > I don't know if it's worth writing that somewhere in a FAQ but for the > record, I wanted to write it here at least. Uli ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Losing mouse click ability and keyboard events
Hello,
The day after, I can testify that changing the power-saving settings on
the server prevented this issue to rise again.
I don't know if it's worth writing that somewhere in a FAQ but for the
record, I wanted to write it here at least.
Have a nice day.
Nicolas
Le 29/09/2020 à 11:49, Nicolas Ecarnot a écrit :
Hello,
Ulrich und Stefan, danke für Ihre Antwort,
Please read below.
Le 28/09/2020 à 22:25, Stefan Baur a écrit :
I don't know if I could run the client and/or the server with additional
verbosity to try to get more hints?
x2goclient --debug >~/x2godebug.log 2>&1
On the server, you can edit /etc/x2go/x2goserver.conf and replace
loglevel=debug
This will increase the verbosity of x2goserver's syslog entries.
Ok, I added those two verbosity parameters, and though it does tells me
tons of additional things at start, they then keep quiet so far.
I noticed that the "no click" issue is appearing some times after a
inactive moment, so that could confirm Stefan's feeling about some power
saving actions...
This morning, I ran the usual setup, just adding the verbose setup
described above, and let it sleep until the "no click issue" arose.
In the logs, I saw nothing at all.
Not a line, nothing.
Does that look like something familiar?
You are actually the third to encounter this issue; sadly, the other two
couldn't be bothered to subscribe here to report the bug.
It seems to be a server-side issue, using Ubuntu 20.04 on the server
side is the common part of the reports.
I wonder if maybe there's some kind of sleep/suspend/energy-saver at
work, or maybe some kind of "scrubbing" mechanism (possibly
systemd-related)?
The server machine is a vmWare VM, and I checked in some advanced vmWare
specific settings whether there could be something relevant but I found
none.
Using the vmWare remote console ("vmrc"), I logged in and disabled every
sleep/suspend/energy-saver related parameters I could find.
Then I killed my session and restarted.
I could be too soon to tell, but it's been more than half an hour, and
so far, the issue has NOT come back.
It's disturbing because the energy-saving parameters I changed were made
as a user and not as root, so I don't get why it could improve a
system-wide behaviour?
I've seen such issues in the past, in different contexts, where cron
jobs were unaware of a running X2Go session and did "stupid" things
(like shutting down the server) that affected the session - because to
them, it looked like there are no users logged in.
I checked what cron could have be doing recently but I found nothing I
could blame it for.
Do you think you could set up a test server with Ubuntu 20.04 that does
not have a GUI, and only some very basic X applications like xterm?
Of course I could.
At present, I'm just letting my server some more time to determine
whether the issue has gone or not.
If still present, I'll try your suggestion.
Is gdm (or some other graphical login manager) running on your server?
If so, could you stop it, switch the machine to text-only mode, and see
if that makes a difference?
-Stefan
The server is an XUbuntu 20.04, so the default login manager is LightDM,
and the wm is XFCE.
If needed, I could try to start it with no X at all and keep testing.
Stay tuned, more to come.
Have a nice day.
--
Nicolas Ecarnot
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Losing mouse click ability and keyboard events
Hello,
Ulrich und Stefan, danke für Ihre Antwort,
Please read below.
Le 28/09/2020 à 22:25, Stefan Baur a écrit :
I don't know if I could run the client and/or the server with additional
verbosity to try to get more hints?
x2goclient --debug >~/x2godebug.log 2>&1
On the server, you can edit /etc/x2go/x2goserver.conf and replace
loglevel=debug
This will increase the verbosity of x2goserver's syslog entries.
Ok, I added those two verbosity parameters, and though it does tells me
tons of additional things at start, they then keep quiet so far.
I noticed that the "no click" issue is appearing some times after a
inactive moment, so that could confirm Stefan's feeling about some power
saving actions...
This morning, I ran the usual setup, just adding the verbose setup
described above, and let it sleep until the "no click issue" arose.
In the logs, I saw nothing at all.
Not a line, nothing.
Does that look like something familiar?
You are actually the third to encounter this issue; sadly, the other two
couldn't be bothered to subscribe here to report the bug.
It seems to be a server-side issue, using Ubuntu 20.04 on the server
side is the common part of the reports.
I wonder if maybe there's some kind of sleep/suspend/energy-saver at
work, or maybe some kind of "scrubbing" mechanism (possibly
systemd-related)?
The server machine is a vmWare VM, and I checked in some advanced vmWare
specific settings whether there could be something relevant but I found
none.
Using the vmWare remote console ("vmrc"), I logged in and disabled every
sleep/suspend/energy-saver related parameters I could find.
Then I killed my session and restarted.
I could be too soon to tell, but it's been more than half an hour, and
so far, the issue has NOT come back.
It's disturbing because the energy-saving parameters I changed were made
as a user and not as root, so I don't get why it could improve a
system-wide behaviour?
I've seen such issues in the past, in different contexts, where cron
jobs were unaware of a running X2Go session and did "stupid" things
(like shutting down the server) that affected the session - because to
them, it looked like there are no users logged in.
I checked what cron could have be doing recently but I found nothing I
could blame it for.
Do you think you could set up a test server with Ubuntu 20.04 that does
not have a GUI, and only some very basic X applications like xterm?
Of course I could.
At present, I'm just letting my server some more time to determine
whether the issue has gone or not.
If still present, I'll try your suggestion.
Is gdm (or some other graphical login manager) running on your server?
If so, could you stop it, switch the machine to text-only mode, and see
if that makes a difference?
-Stefan
The server is an XUbuntu 20.04, so the default login manager is LightDM,
and the wm is XFCE.
If needed, I could try to start it with no X at all and keep testing.
Stay tuned, more to come.
Have a nice day.
--
Nicolas Ecarnot
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
Re: [X2Go-User] Losing mouse click ability and keyboard events
Am 28.09.20 um 21:41 schrieb Nicolas Ecarnot: > Hello, > > First post, thank you for welcoming me here. > From an Ubuntu 20.04 client to an Ubuntu 20.04 server, the default > repository install is working out of the box, all is nice. > > But from times to times (random but around 15 min. ), with no obvious > reasons, I'm losing the ability to click : [...] > I don't know if I could run the client and/or the server with additional > verbosity to try to get more hints? On the client, you can run: x2goclient --debug >~/x2godebug.log 2>&1 On the server, you can edit /etc/x2go/x2goserver.conf and replace loglevel=notice with loglevel=debug This will increase the verbosity of x2goserver's syslog entries. > Does that look like something familiar? You are actually the third to encounter this issue; sadly, the other two couldn't be bothered to subscribe here to report the bug. It seems to be a server-side issue, using Ubuntu 20.04 on the server side is the common part of the reports. I wonder if maybe there's some kind of sleep/suspend/energy-saver at work, or maybe some kind of "scrubbing" mechanism (possibly systemd-related)? I've seen such issues in the past, in different contexts, where cron jobs were unaware of a running X2Go session and did "stupid" things (like shutting down the server) that affected the session - because to them, it looked like there are no users logged in. Do you think you could set up a test server with Ubuntu 20.04 that does not have a GUI, and only some very basic X applications like xterm? Is gdm (or some other graphical login manager) running on your server? If so, could you stop it, switch the machine to text-only mode, and see if that makes a difference? -Stefan -- 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 ___ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
