GNOME Bugzilla – Bug 685918
screen not locked on lid close
Last modified: 2015-06-13 11:32:09 UTC
(Unsure where in the g-s/g-s-d stack this lies. Feel free to move) I have the following settings: Turn screen off after: 10 minutes Lock screen [on] Lock screeen after: screen turns off On lid close: nothing When I close the lid, the screen turns off. But it's not locked. It should be. Setting lid close to 'blank' doesn't appear to fix it either. gnome-settings-daemon-3.6.1-2.fc18.x86_64 gnome-shell-3.6.0-1.fc18.x86_64 gnome-screensaver-3.6.0-1.fc18.x86_64
*** Bug 686132 has been marked as a duplicate of this bug. ***
Bill, are you still seeing this ? I'm pretty sure we've fixed this in 3.6.1
3.6.1 isn't pushed yet... when it is, I'll try.
Persists with 3.6.1.
Is this a multi-monitor situation ? Or are you talking about the laptop panel ? Is the machine not suspending on lid close ?
(In reply to comment #5) > Is this a multi-monitor situation ? > Or are you talking about the laptop panel ? even with single laptop panel the problem persists. > Is the machine not suspending on lid close ? It _is_ suspending and I am not sure who is in charge for this. systemd manages PM on his own.
In my case, it's a single laptop panel. It's not suspending on lid close, because I have it configured not to.
> It's not suspending on lid close, because I have it configured not to. The 'On lid close' settings should not have any effect anymore - the power plugin is not reading that setting at all, in 3.6.1-2. The only key that has an effect on lid close nowadays is lid-close-suspend-with-external-monitors, or whatever it is called. So, thats mysterious already.
What I've till now: 1. at times of 3.4 everything worked: closing lid suspended+locked 2. now Shell upgraded to 3.6 together with systemd and upower. I guess that something bad happened with Shell or upower or with their interaction. Another possibility is to hack systemd-sleep(8).
You have it set to do nothing or blank on lid close, so why would you expect it to lock? Unless you mean it doesn't lock after 10 minutes? That worked for me in 3.4 and still works with 3.6. With 3.6, I had to change the systemd config to ignore the lid close so it doesn't suspend. But the screen still locks after the expected idle time.
The checkbox is to lock screen "after screen turns off". The screen turns off when you close the lid, so it should lock.
That checkbox is related to the one above it regarding turning the screen off. I don't know for sure, but I expect it's the laptop hardware that turns the backlight off when you close the lid, not the OS.
Which is an interesting bit of semantics that doesn't matter to the user using the system with the options presented.
In GNOME 3.7, we have: - automatic screen lock - lock screen after [screen turns off] There's no "what to do on lid close" anymore, and it's not possible to get the screen to turn off without either 1) another screen being plugged in 2) idle being reached. The shell will lock the screen when idle is reached with the above setting. I'm not sure there's anything left to do here. even if I agree that this should have worked in older versions where "on lid close" did something.
Can't it catch the 'screen turns off' event and lock the screen? Is there not a hotplug event in X when the lid close turns off the display?
Then is there a period of time when the screen is already dimmed down but isn't locked yet (2-5 sec): to have a last chance to prevent locking?
There is supposed to be an option to delay the locking, but it doesn't work any more. (Bug 654667)
(In reply to comment #15) > Can't it catch the 'screen turns off' event and lock the screen? Is there not a > hotplug event in X when the lid close turns off the display? This isn't the problem. In which cases would we have a closed lid where no external display is in use, and where we'd want to have the whole session locked? (In reply to comment #17) > There is supposed to be an option to delay the locking, but it doesn't work any > more. (Bug 654667) gnome-screensaver isn't used anymore.
(In reply to comment #18) > (In reply to comment #15) > > Can't it catch the 'screen turns off' event and lock the screen? Is there not a > > hotplug event in X when the lid close turns off the display? > > This isn't the problem. In which cases would we have a closed lid where no > external display is in use, and where we'd want to have the whole session > locked? All the cases where you're not suspending on lid close.
(In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #15) > > > Can't it catch the 'screen turns off' event and lock the screen? Is there not a > > > hotplug event in X when the lid close turns off the display? > > > > This isn't the problem. In which cases would we have a closed lid where no > > external display is in use, and where we'd want to have the whole session > > locked? > > All the cases where you're not suspending on lid close. Except that there isn't such a case unless you're rolling your own settings (in which case, well, you get to lock your own screen too), or you have an external display. If you have an external display, you probably don't want to make the other display unusable by locking it. Did I miss something?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!