GNOME Bugzilla – Bug 598118
Screensaver lock-on-suspend policy inconsistent with gnome-power-manager
Last modified: 2021-06-14 18:20:33 UTC
Now suspend and hibernate actions are no longer proxied through gnome-power-manager, gnome-session is currently responsible for locking the screen when suspending from the session dialog (whereas gnome-power-manager used to take care of this in previous releases). gnome-session looks at /apps/gnome-screensaver/lock_enabled to determine whether to lock the screen on suspend. This means the new behaviour differs from pre-2.28 releases, because gnome-power-manager has it's own settings for screen locking (although it can also be configured to use /apps/gnome-screensaver/lock_enabled) The new behaviour seems to be confusing users, as some people are disabling "Lock screen when screensaver is active" in the screensaver preferences, but still expecting their screen to lock when they suspend from the session dialog (as it did in previous releases)
Subscribing hughsie as requested by vuntz on IRC: vuntz: chrisccoulson: please cc hughsie in the bug you open, btw. Just so that he double-checks
I'll gladly move the gnome-power-manager *lock* keys to GNOME session if vuntz is okay with that, but it adds a little complexity. Personally I would just keep the single checkbox for policy for screen lock and suspend. If you're paranoid about people logging in as you after the screensaver has timed out, then you should probably be paranoid at people resuming it from sleep for you.
Having them in gnome-session won't help other DK-power users :-) It should really just be handled in the devkit-power-glib library, imho.
I think there is a difference between "I left my computer idle so the screen should turn off to save power" and "I put my computer to sleep and put it in my bag" such that having your screen lock in the second case is useful for if someone picks that computer up.
note if we make that distinction then gnome-shell will need to be updated, too... I agree with vuntz that it would be good if this policy was all defined in one place.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of gnome-session, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-session/-/issues/ Thank you for your understanding and your help.