[Bug 1778817] Re: release upgrade from xenial to bionic desktop: screen locks itself, password to unlock fails

[Sebastien Bacher]

> Ok, but we still need to know how to inhibit the screen locking in compiz,
> since the previous standard method is ineffective.

The command that Julian pointed out as the one used by u-r-u is correct
and works from our testing


> unless you are running a GNOME session.

> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-
upgrader/trunk/view/head:/DistUpgrade/DistUpgradeQuirks.py#L444

It looks like Unity sessions are in a similar situation so maybe the
code should be change to keep the inhibitor for those as well (maybe
poping up a dialog explaining that screen lock is not going to work
until reboot if that's less confusing to users?). That's a different
case than the one reported here though

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

Title:
  release upgrade from xenial to bionic desktop: screen locks itself,
  password to unlock fails

Status in compiz package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in compiz source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged

Bug description:
  During a release upgrade, the screen should not be locked because the
  upgrade of underlying libraries may leave the system in an
  inconsistent state where the process locking the screen may not be
  able to unlock it again.

  There is code in the ubuntu-release-upgrader to handle this
  (DistUpgrade/DistUpgradeQuirks.py:DistUpgradeQuirks._inhibitIdle).

  I have just started a release upgrade of an Ubuntu desktop from xenial
  to bionic with update-manager -d.  After leaving it unattended for a
  while, I came back to find the screen was locked.

  /var/log/auth.log includes messages such as:

  Jun 26 16:00:45 epona compiz: PAM unable to dlopen(pam_unix.so):
  /lib/security/pam_unix.so: cannot open shared object file: No such
  file or directory

  This indicates a problem dlopen()ing the PAM modules (actual path:
  /lib/x86_64-linux-gnu/security/pam_unix.so) because some ABI has
  changed in the system libraries, and the copy loaded into the running
  compiz process does not have the symbols required in order to run this
  module.

  This is the exact reason the screensaver is supposed to be inhibited
  on upgrade.

  This is also why every sensible screensaver spawns a fresh helper
  process to handle the authentication through PAM.  compiz (unity),
  apparently, does not.

  I do not yet know what symbols have changed to cause this failure.
  I'm still investigating that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1778817/+subscriptions