Automatic screen blank/lock sends lock signal even if it is cancelled during fade-out
Affected version
- OS: Arch Linux x86-64, kernel 5.19.6
- GNOME shell version: 42.4
- Appears on X11/XOrg (likely also in Wayland)
Bug summary
When requested to blank and lock the screen after several minutes through the energy settings, the lock signal will be propagated to all applications as soon as the screen starts fading out, rather than when the fade-out is complete.
Steps to reproduce
- Open the settings panel.
- Go to the Energy tab.
- Enable automatic screen blanking/locking after a minute or so.
- Wait for the time to expire.
- Observe the fade-out starting. (The lock signal propagates to applications.)
- Cancel the locking by moving the mouse.
What happened
The signal that GNOME is about to lock the session happened even though the lock was cancelled before it happened.
What did you expect to happen
The signal is not propagated until the very last moment where the session actually locks.
Relevant logs, screenshots, screencasts etc.
This is especially noticeable with an application such as KeePassXC when, under the Security panel, you have the option enabled where the database locks itself when the user session does. If you are idling in your chair, see your desktop is about to lock, and cancel the fadeout, it is already too late: the database has locked.
If this is a KeePassXC-specific issue, my apologies. It seemed like a more general issue, hence the report here first.