Created attachment 150212 [details] journal log SUMMARY System hang (not accepting keyboard/mouse input) after left unattended for a few minutes STEPS TO REPRODUCE Run KDE/Plasma on Wayland, Do nothing and wait until displays are timed-out. Wait for a few more minutes. OBSERVED RESULT System hang (not accepting keyboard/mouse input) In journal log there's autorandr repeatedly failing. Removing autorandr just gets rid of the error message but the hang remains. Doesn't not happen on X11, Doesn't not happen with Sway. Couldn't test with GNOME since I couldn't get GNOME to turn off my displays at all. EXPECTED RESULT System continues to function as normal, being able to wake up the displays with keyboard/mouse
What version of Plasma/KWin are you using?
(In reply to Nate Graham from comment #1) > What version of Plasma/KWin are you using? KDE/Plasma 5.25.1 on Arch Linux Wayland 1.20.0
How about you disable autorandr? It shouldn't have an effect on KWin Wayland anyway. Do you know if KWin is crashing? Could you provide us with kwin logs and maybe backtraces?
Removing autorandr or disabling it just get rid the error messages in the journal log. The hang still occurs. Sorry that I can't provide more detailed information since I'm clueless about why this occurs as well. I don't believe KWin crashed, if I had music playing in the background it would continue to play during the hang. The system just won't accept any keyboard mouse input and so the display won't wake up. (Even caps lock won't work) I'm on Nvidia Ampere gaming GPU, could it be an issue with Nvidia, drm and KDE interacting badly somehow?
What we generally do in these cases is ssh into the system and gdb-attach to kwin_wayland to see if it's stuck. Checking dmesg output would also be useful, especially if it includes the drm extra bits.
I have setup sshd just to find out I cannot reproduce this bug anymore. The autorandr things still show up in log but system no longer hangs. Not sure what happened before but I'm closing this for now. If I have to guess I'd say it was a badly configured usb auto suspend policy causing keyboard/mouse to stop functioning. Not sure though.