[Bug 966451] Re: When xscreensaver/xlockmore isn't properly stopped, the upgrade leads to a broken system

[dah bien-hwa]

The dialog regarding xscreensaver/xmorelock just was shown to me when
trying to upgrade from 20.04 to 21.10 (running do-release-upgrade in the
shell). Upgrade is still running, keeping fingers crossed it will work
properly.

As there is no information on how to properly disable
xscreensaver/xmorelock, I find this message a bit unhelpful. To
exaggerate, it reads like "The installation might go wrong and lock
yourself out of the system. If you want to prevent that, then go find
out by yourself how to do that. Good Luck!"

-- 
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/966451

Title:
  When xscreensaver/xlockmore isn't properly stopped, the upgrade leads
  to a broken system

Status in Software Updater:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete

Bug description:
  During the installation, the following message is shown:

  "Configuring libc6
  xscreensaver and xlockmore must be restarted before upgrading
  One or more running instances of xscreensaver or xlockmore have been detected on this system. Because of incompatible library changes, the upgrade of the GNU libc library will leave you unable to authenticate to these programs. You should arrange for these programs to be restarted or stopped before continuing this upgrade, to avoid locking your users out of their current sessions."

  If you close the window by clicking the close button, the installation
  is broken. However if you click "Continue", the installation proceeds
  normally.

  Affected upgrades include:
  – Lubuntu 11.10 to 12.04 (i386)
  – Lubuntu 12.10 to 13.04 (i386 and amd64)
  – Can be confirmed on Xubuntu upgrades as well

  Preferred solution:
  The installer should be able to stop xscreensaver and xlockmore automatically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/update-manager/+bug/966451/+subscriptions