[Bug 1174093] Re: notify user that the lock screen has been disabled

[Brian Murray]

** Summary changed:

- disable screensaver locking at start of upgrade
+ notify user that the lock screen has been disabled

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1174093

Title:
  notify user that the lock screen has been disabled

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  I set an upgrade running from 12.10 to 13.04 (my second attempt, the
  first had failed due to loss of network), and as I expected this to
  take some time, locked the screen and left.  I returned to an
  _unlocked_ screen, which is obviously a security risk.

  It was showing a debconf dialog (asking if I wanted to restart cron,
  atd, cups and rsync after upgrading libc6, probably not the most
  helpful thing to ask a user who may well have no idea what these are),
  but the logs suggest update-manager deliberately kills gnome-
  screensaver before starting the install phase (possibly a fix for bug
  319332 or similar problems?).

  If it is not practical to have screen lock actually working during an
  upgrade, I suggest either disabling it right at the start and giving
  an appropriate message if the user tries it, or pausing and waiting
  for user input if the screen is locked at the point where the lock
  needs to be disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1174093/+subscriptions