Created attachment 183274 [details] htop SUMMARY After closing and reopening the laptop lid, the `kscreenlocker_greet` process remains active and consumes 100% CPU usage indefinitely. This leads to high CPU temperatures and increased fan activity, even though the screen unlocks normally. STEPS TO REPRODUCE 1. Close the laptop lid (Power settings are set to lock the session on lid close). 2. Wait for a few seconds. 3. Reopen the lid and log back into the session. OBSERVED RESULT - The screen unlocks as expected, but `kscreenlocker_greet` continues running in the background. - It consumes over 100% CPU (confirmed via `htop`). - System temperature rises (my Ryzen 7 7435HS CPU jumps to over 70°C). - I had to manually terminate it with `pkill kscreenlocker_greet`. EXPECTED RESULT - `kscreenlocker_greet` should exit cleanly after unlocking the session. - CPU usage should return to normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (kernel 6.15.5-zen1-1-zen) KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Graphics Platform: Wayland ADDITIONAL INFORMATION - GPU: NVIDIA RTX 4060 Laptop GPU (using dedicated GPU mode, no hybrid graphics) - Laptop: ASUS TUF Gaming A15 FA507NVR - Screenshot of the issue attached (htop showing high CPU usage)
I tried to inspect journalctl logs with filters like grep kscreenlocker and grep lid, but there were no relevant log entries related to the issue. It seems kscreenlocker_greet does not log anything during or after the high CPU usage event.
This is unusual, and I can't reproduce it. You say that the kscreenlocker_greet process persists in the background after you've unlocked the screen?
.
Sorry for the late reply. Yes, that’s correct — the system seemed to wake up very slowly, and when it finally did, the fans were running fast. I checked and saw that kscreenlocker_greet was using very high CPU. I can’t reproduce the issue right now, but if it happens again I’ll provide more feedback and logs. Is there anything specific you’d like me to collect if I encounter it again?
I had a quick look online and it seems that other users have reported similar issues — high CPU usage from kscreenlocker_greet after waking from lid close on Wayland, sometimes with NVIDIA GPUs. I haven’t gone through all of them in detail, but it looks like I’m not the only one who has experienced this.
🐛🧹 ⚠️ 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!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.