[Bug 1174093] Update Released

[Steve Langasek]

The verification of the Stable Release Update for ubuntu-release-
upgrader has completed successfully and the package has now been
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

-- 
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:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Users are not notified that their lock screen is disabled during an upgrade and may left there system in an insecure location during the upgrade process.

  [Test Case]
  1) Configure a screen lock with a short (2 minute?) timeout
  2) Upgrade from Ubuntu 16.04 to Ubuntu 18.04
  3) Observe that the screen is not locked during the upgrade process and you that you were not warned about it

  With the version of ubuntu-release-upgrader from -proposed you will
  receive a dialog telling you the lock screen has been disabled
  immediately before the upgrade begins.

  [Regression Potential]
  A new dialog is being added so there is little chance of regression.

  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