the gnome-session dialog suspend option doesn't lock the screen

Bug #847814 reported by Colin Law on 2011-09-12
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-session
New
Medium
gnome-session (Ubuntu)
Low
Unassigned

Bug Description

If Lock is set to Off in System Settings > Screen then Oneiric does not ask for a password on suspend resume. A user that is required to enter a password at login/startup should always be asked for the password on resume.
The situation for re-enabling the screen after a period of inactivity is quite different, only that should be controlled by Screen > Lock.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.91-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Mon Sep 12 14:03:38 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
 deja-dup 19.91-0ubuntu3
 empathy 3.1.91-0ubuntu2
 gnome-bluetooth 3.1.4-0ubuntu1
 indicator-datetime 0.2.93-0ubuntu2

Colin Law (colin-law) wrote :
Colin Law (colin-law) wrote :

It appears that this may be a resurrection of bug #446191 that was much discussed then fixed in Karmic but seems to be back for Oneiric.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, how do you suspend? (indicator, lid close, ...)

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Colin Law (colin-law) wrote :

I thought that this happened however I suspended but I now find that it is ok if I select suspend from the indicator but if I press the power button and select suspend from the popup then it does not ask for password on resume. I cannot try closing the lid as suspend/resume via lid operation does not work on this laptop.

Sebastien Bacher (seb128) wrote :

seems like a gnome-session issue then

affects: gnome-control-center (Ubuntu) → gnome-session (Ubuntu)
Changed in gnome-session (Ubuntu):
status: Incomplete → New
Sebastien Bacher (seb128) wrote :

seems a bit similar to bug #859498

Sebastien Bacher (seb128) wrote :

Subscribing Marc, he usually loves screen locking bugs ;-)

summary: - Oneiric not asking for password after suspend / resume
+ the gnome-session dialog suspend option doesn't lock the screen
Colin Law (colin-law) wrote :

It does seem extremely similar to bug #859498, I see the NM disconnect for example. I am still seeing it with gnome-settings-daemon 3.2.0-0ubuntu4 if that is relevant.

Marc Deslauriers (mdeslaur) wrote :

I've committed a patch for this to bzr.

Changed in gnome-session (Ubuntu):
status: New → Fix Committed
Daniel Hahler (blueyed) wrote :

This has landed in Oneiric:

gnome-settings-daemon (3.2.0-0ubuntu5) oneiric; urgency=low

  [ Rodrigo Moya ]
  * debian/patches/00git_avoid_undesired_sleeps.patch:
    - Avoid sleeping the computer when disabled (LP: #864479) and ditto for
      the display (LP: #863038)

  [ Marc Deslauriers ]
  * debian/patches/51_always_lock_screen_on_suspend.patch:
    - always lock the screen when suspending or hibernating, even if
      automatic screen lock is disabled. (LP: #847814)

 -- Marc Deslauriers <email address hidden> Mon, 03 Oct 2011 17:23:23 -0400

Changed in gnome-session (Ubuntu):
status: Fix Committed → Fix Released
Changed in gnome-session:
status: New → Invalid
Carey Underwood (cwillu) wrote :

Did this really need to be hardcoded into a binary though? There are valid use cases for not locking the screen on a closed lid, one of which was mentioned in passing in the original bug report: the case where the user is automatically logged in.

A crappy workaround involves "chmod a-x gnome-screensaver" followed by "killall gnome-screensaver".

Marc Deslauriers (mdeslaur) wrote :

We will be discussing this at UDS, and doing something better for the next release.

Lukáš Chmela (lukaschmela) wrote :

By the way, I would like to mention that there is a similar, possibly related bug report concerning locking the screen when the lid is closed (without hibernation) - bug #871047

David F. (malteworld) wrote :

Since Oneiric/Gnome 3 my session doesn't lock on suspend even though it *is* set to lock after 30 minutes.

Dirk Mcbratney (djmcbratney) wrote :

Under Gnome Shell with the screenlock disabled, this behavior is highly irritating, because the Gnome session menu follows my settings and does not lock the screen, but using the power button does lock the screen. I don't have much of a "use case" for a screen lock for a machine sitting safely in my apartment. The screen lock setting should reasonably be universal (and can still be set with "never" as the timeout for inactivity either way.)

Changed in gnome-session:
importance: Undecided → Unknown
status: Invalid → Unknown
Changed in gnome-session:
importance: Unknown → Medium
status: Unknown → New
David F. (malteworld) wrote :

My screen disables after 10 and the shell locks after 30 minutes as configured in the settings. When using the suspend functionality in the g-s user menu, I experience the same symptoms as https://bbs.archlinux.org/viewtopic.php?pid=1007305#p1007305.
If I do however make the changes in the patch, everything works as I expect. I don't know though, if this behaves correctly™ in other use cases.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.