desktop-packages team mailing list archive

[Joel Ebel <620693@xxxxxxxxxxxxxxxxxx>]

Martin, this new package looks good on Lucid.  I went through the
testing procedure before the package, and the screen did not lock.
After installing the new package, without changing settings, the screen
did indeed lock.

Michael, thanks for taking a look at this.

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

Title:
  Screen not locked when turned off

Status in “gnome-power-manager” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” source package in Lucid:
  Fix Committed

Bug description:
  Binary package hint: gnome-power-manager

  All settings I refer to here are gconf settings relative to /apps
  /gnome-power-manager unless fully qualified.

  If the value for timeout/sleep_display_ac (in seconds) is less than
  that of /desktop/gnome/session/idle_delay (in minutes) then the screen
  is blanked before the screensaver is activated.

  gnome-power-manager offers gconf options, described in its manual, for
  causing the screen to be locked when the screen is blanked.  This can
  in theory be set by enabling lock/blank_screen or enabling
  lock/use_screensaver_settings if /apps/gnome-screensaver/lock_enabled
  is set.

  The problem is that neither of these settings appear to work.  As a
  result, if the screen is blanked before the screensaver starts, or if
  the screensaver is disabled entirely, the screen does not get locked
  when blanked.  These settings do not appear to behave as described in
  the manual.

  The manual also describes that power management timers begin only
  after session idle, but that doesn't appear to be the case anymore.
  power management timers now appear to start immediately, independent
  of session idle_delay.  This documentation should be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions