desktop-packages team mailing list archive

[Carey Underwood <cwillu@xxxxxxxxxx>]

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".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/847814

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

Status in The GNOME 2 Session Manager:
  Invalid
Status in “gnome-session” package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/847814/+subscriptions