> I might be a bit naive here, but couldn't you simply always lock the screen on suspend in Unity is being run, and always respect the "lock screen" option if a gnome-shell session is being run?
Could you describe your user scenario? Do you use autologin or enter a password on boot? In which case do you want to see the screen locked and which cases not? We could make the behavior session specific but that's not what we aim for, we aim at a good and comprehensive behaviour. If you want to not be bothered with passwords you usually use autologin and will not get any locking for example. If you do care about security and set your box to enter a password on login you probably want a password on resume as well (it's not very different from boot). It's easier to explain to users that their box will use automatic locking in a consistent way, or not do any locking without user asking for it. Do you think there are sceharios where locking should happen in some actions and not others? Would that still seem "logical" to users? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/869765 Title: Screen locked on lid close, suspend, user switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
