http://bugzilla.opensuse.org/show_bug.cgi?id=1209224 Bug ID: 1209224 Summary: xrdp idle issue after updating to TW 20230222 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs@suse.de Reporter: jmscdba@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After updating to TW 20230222 xrdp was updated from version 0.9.20-5.1.x86_64 to 0.9.20-6.1|x86_64. Starting a new xrdp session from another Linux machine, a Windows 10 machine using MS RDP client, or even from my local machine ( but as a different user ) to the xrdp service on my local machine all connect and work perfectly fine for as long as you want to use them, however, if you let the rdp session sit for a while then when you come back to it the desktop is black and the session is no longer responsive. Originally to recover, I had to kill the processes for the user and also restart the xrdp service. After doing that, then rdp works fine again ( from any of the sources ) until you leave the session sit idle and the problem reocurrs. This did not occur with previous xrdp versions and I am using the stock xrdp configuration without any changes. It was suggested to check /etc/xrdp/sesman.ini to check DisconnectedTimeLimit and IdleTimeLimit but they are both set to the default of 0 which disables disconnection. Yesterday, while trying to debug this further so that I would have more information I came across what I believe is the source of the problem. In System Settings / Power Management / Energy Saving, on the On AC Power Tab, the Screen Energy Saving is checked and it is set to switch off after 10 min. This is the default setting and used by all users, HOWEVER, if I turn that off then xrdp no longer has the issue and the session can be left idle for as long as you like. Looking at my zypper history, I see that powerdevil5 was updated from 5.26.5-1.1 x86_64 to 5.27.0-1.1 x86_64 so I suspect that is the real source of the problem since turning off Screen Energy Saving stops the problem from occurring. Here is my KDE version info: KDE Plasma Version 5.27.0 KDE FrameWorks Version 5.103.0 Qt Version 5.15.8 Please let me know if you need any additional information or logs -- You are receiving this mail because: You are on the CC list for the bug.