SUMMARY Title. I had 30 minutes until system locks AND suspends, after unsuspending I can't unlock it, Enter does nothing, it doesn't even check the password. I changed both to 1 minute for testing and it reproduced the issue. STEPS TO REPRODUCE 1. Go to settings 2. Find and set autolock to 1 minute 3. In power management, set idle to suspend after 1 minute OBSERVED RESULT After waking up lockscreen can't be unlocked. EXPECTED RESULT The thing lockscreen should do SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU ADDITIONAL INFORMATION Luckily I can click "switch user", which throws me to SDDM and there I can log back into my session without losing anything
I can't reproduce this using the steps outlined on master - the lock screen allows unlocking without issues. Does the same thing happen if you manually put the computer to sleep (using e.g. the "Sleep" button in the Application Launcher)?
Nope, it happens only when it locks/suspends at the same time while being idle. Theoretically, I could try to do the same (suspend and lock at the same time) using terminal, but idk how. It also doesn't occur when suspend and autolock have different timers: lock after 1 minute, suspend after 2 minutes or vice versa.
(In reply to Damglador from comment #2) > It also doesn't occur when suspend and autolock have different timers: lock > after 1 minute, suspend after 2 minutes or vice versa. I suspected so and made sure both had the same timers. Odd. Does it happen every time, or only sometimes?
It happened every time I tested it. It also happens with all suspend modes, but since hybrid suspend and suspend then hibernate don't work for me, system instantly wakes up, I have suspend mode set to just suspend to RAM. Before going to sleep monitor also briefly shows the lock screen wallpaper. Huh. I've discovered another fun thing. If I let the lock screen idle for a bit, so it hides the login prompt, and then get back to the login prompt, it works just fine. I also have disabled lock after waking up from suspend, and enabling it "fixes" the issue, but introduces a bunch of other funky bugs: avatar is not a circle, but a square, background blur isn't applied on the login prompt, power buttons have a weird background. Disabling autolock and leaving just lock after suspend makes everything work normally: blur is applied, power buttons look like they should, avatar is a circle and the lock screen can actually be unlocked.
Created attachment 178647 [details] lock after suspend+ autolock matching suspend timer Here's a photo of how it looks with lock after suspend and autolock enabled and set on the same time as suspend
Created attachment 178648 [details] how it looks normally
Thanks. I'm out of ideas at this point and will leave it for someone else to investigate. You can leave this on reported while there are no more open questions, so that other triagers and developers see it.
It looks like the lock screen has fallen back to software rendering. This often implies a GPU reset or crash.
Weird that it happens under such specific conditions: having lock after suspend enabled, with suspend and autolock set to the same time. I also didn't notice any GPU or graphics related issues after the lock screen.
Hi - based on Nate's idea - does the issue occur if you boot with the Nouveau drivers for your NVIDIA card, instead of the proprietary ones?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Blacklisted nvidia drivers in modprobe.d and the issue didn't occur. Sorry for responding so late.
Can you confirm that your system is set up according to https://community.kde.org/Distributions/Packaging_Recommendations#Proprietary_NVidia_driver_configuration? Does that fix it if you un-blacklist the proprietary NVDIA drivers?
nvidia-suspend, nvidia-hibernate and nvidia-resume were enabled. Suggested kernel parameters are set by default on Arch. And I checked on my system, they are Probably unrelated, but there was also nvidia-suspend-then-resume. Enabling, which fixed suspend then hibernate, but lead to some funky side effects, so I kept it off and switched back to simple suspend. It also did not fix the issue.
Oh, fun fact: wiggling the mouse while it wakes up from this bug just automatically unlocks the lock screen. That doesn't happen with "Lock after suspend" option and autolock disabled
I'll leave it at "Nvidia being Nvidia", at least for now.