I have seen similar behaviour on Centos, also with kde. It seems that plasma-desktop is running wild. You can probably mitigate the problem a bit by adding this to /etc/x2go/x2goagent.options X2GO_NXOPTIONS="sleep=0"
You can also try to kill and restart the plasma-desktop but at the moment I do not remember how that can be done. Try to search for the process that takes up all the cpu and google it.
Uli
On Tue, May 4, 2021 at 11:07 AM Thomas Roebbenack <res1@embeddedjava.de> wrote:
Is there any problems known about frozen sessions at reopen it after a some time?
This problem occurs since 3 days now, don't know why and what exactly happen (probably system updates). Before it worked without problems.
I working on "Ubuntu 20.04.2 LTS" and KDE Plasma Desktop (5.18.5) (Framework 5.68.0, QT 5.12.8)
What exactly happen:
Open a session working as expected (with opened Session/Window the Screenlocker occurs, but I can move the mouse and enter the password)
After closing the window (the session runs in the background), I can reconnect after a short time ~10 Minutes, the screenlocker occurs, but I can move the mouse and enter the password.
But, after a longer time (don't know exactly how long), If I reconnect the screenlocker occurs, but the screens seems to be frozen. I can move the mouse, nothing happen, try to enter some keys, nothing happen. Looks like the screensaver is dead. The CPU load of 1 core is 100% (kscreenlocker_greet + a x11 process).
-> The only thing that worked at the moment, try to open a second session gives me the possibility to close the first one, than I can reconnect. But I have to kill (-9) the both running processes to stop feed my CPU load.
-> Disable the screensaver is no option, because there exists a directive to use it.
Any suggestions? Any Ideas? Thank you in advance.
Thomas
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user