Ubuntu

in gutsy, screen locks on lid close even when gconf option is turned off

Reported by ddumanis on 2007-10-09
12
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Low
Unassigned
Declined for Gutsy by Henrik Nilsen Omma

Bug Description

When "screen lock on lid close" is unchecked in gconf editor's gnome-power-manager options, the screen STILL locks on lid close!

No option to fix in power manager GUI or screen saver GUI either.

ddumanis (dave-davedumanis) wrote :

Sorry, I meant "screen lock on suspend," "screen lock on blank," etc. in gconf-editor. But the bug still holds true.

ddumanis (dave-davedumanis) wrote :

Discovered a SECOND set of totally redundant screenlock-related checkboxes that are in the "lock" folder of gnome-power-manager section of gconf--not at the root level of the gnome-power-manager section of gconf. The ones in the "lock" folder actually work!

So, this is really a USER INTERFACE BUG--screenlock should be toggleable from the GUI of power manager, or the GUI of screensaver, or both--not (a) only from gconf and (b) from two different sets of checkboxes, only one of which work.

unggnu (unggnu) wrote :

I can confirm this. I think the greatest option for this is /apps/gnome-power-manager/lock/use_screensaver_settings . If people want locking they enable screensaver locking which results in locking for suspend, hibernate and so on but people who don't want enter their password every time disable locking and everything is fine.
It makes no sense for me to open gconf-editor to disable locking per hand if there is such an option.
I have made a debdiff for it.

unggnu (unggnu) on 2007-10-12
Changed in gnome-power-manager:
status: New → Fix Committed
unggnu (unggnu) on 2007-10-14
Changed in gnome-power-manager:
status: Fix Committed → Confirmed
Oliver Grawert (ogra) wrote :

unuggu: that patch is a major change in the default security policy (no locking for anybody instead of locking for everybody after suspend/hibernate), please discuss such massive changes with the security people via the ubuntu-devel-discuss or ubuntu-devel lists first.

to the initial reporter: can you please test if version 2.20.0-0ubuntu6 gnome-power-manager fixes it for you (if the release managers approve the upload)

unggnu (unggnu) wrote :

The standard ubuntu settings locks everything which makes no sense imho. Maybe screensaver locking should be activated per default so it would give same security like before but more flexibility.

Oliver Grawert (ogra) wrote :

now you switched on locking for everybody and every screensaver action as well ... solving that problem in a proper balance between usability and security isnt that easy ...

unggnu (unggnu) wrote :

The assumption is that people who want to protect their computer after suspend or hibernate want a locking screensaver too.
I mean who wants suspend/hibernate password protection when he doesn't care that PC is locked after some time automatically. Btw. they can disable the screensaver without messing up with the suspend and hibernate security. In this case Ubuntu would gain some more security through screensaver locking.
If I want a password free working (many people at home prefer this) I only need to change two GUI options (screensaver locking and gdm) and if I don't there is no change needed. That is usability for me and much more intuitive than the weird Gnome screensaver sleeping time assumption which make the differentiation between ac and battery power useless.

Oliver Grawert (ogra) wrote :

as i saied in my mail to ubuntu-devel-discuss already, i'm open for any change in behavior as long as the security and desktop teams agree, please lets see how teh discussion turns out so we can change it for hardy note that i wont change a default behavior we used in released versions before without a confirmation from usability and security side and especially not so short at the end of a release cycle.

fate (warpman-gmx) wrote :

<<If I want a password free working (many people at home prefer this) I only need to change two GUI options (screensaver locking and gdm) and if I don't there is no change needed. That is usability for me and much more intuitive than the weird Gnome screensaver sleeping time assumption which make the differentiation between ac and battery power useless.>>

I totally aggree with the above statement.
It's not understandable that even after unchecking screensaver lock, it sometimes lock the screen... it's annoying if you ask me und has nothing to do with security here cause you can check "always lock screensaver" to gain max security.

Henrik Nilsen Omma (henrik) wrote :

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage .

Changed in gnome-power-manager:
importance: Undecided → Low
Scott Howard (showard314) wrote :

Does this bug still exist in Jaunty (or Karmic)? What's the status with the discussions with desktop and security developers?

Changed in gnome-power-manager (Ubuntu):
status: Confirmed → Incomplete
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information?

Does this bug still exist in Lucid (or Maverick)?

Thanks.

Leo Arias (elopio) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers