[BUG] Lock Screen not Kicking In
Describe the bug
Hello. When I close my lid on my Lenovo and it goes to sleep, when I open it it's right where I left off with no Lock Screen.
This is obviously a big security problem. Is this expected behavior?
Steps to reproduce
- Close lid
- Wait a while
- Open lid. Lock Screen not presented.
Expected behavior
Lock Screen should appear after lid is closed and laptop sleeps.
Screenshots
No response
Distribution
Arch Linux
If Other, specify
No response
Additional context
No response
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Hi. This depends on your laptop. On my laptops everything works fine. Please use this file as a starting point. https://github.com/mylinuxforwork/dotfiles/blob/main/share/dotfiles/.config/hypr/hypridle.conf
The configuration of hypridle must be done by the user. It is impossible to provide a standard configuration for all systems.
@mylinuxforwork Seeing nearly the same behavior here when using the mentioned hypridle.conf. Except that I see my desktop for a few seconds an then the lock screens kicks in. I can't interact with the desktop for this short period of time. The problem only appears, if the system was sleeping for several hours. If I suspend it and wake it up after a few minutes the first thing that appears is the lock screen.
It could be something that is dependent on sleep states of the processor (using a Lunar Lake notebook), because in my case the system also feels very sluggish for the first half a minute, if I wake it up after several hours/ days. And that seems to be the window in which the lock screen isn't visible for a few seconds. @sibblegp Is this the same for your system? You described it as if the lock screen doesn't show up at all.
My Linux knowledge isn't so advanced that I know if this is the normal way how Linux works in combination with a window manager (hyprland)/ display manager (sddm), but I never saw an other desktop environment where you could see a glimpse of the desktop. The lock screen should appear first, regardless of what's happening with the rest of the system. I don't know if it under your control @mylinuxforwork how these parts work together?