[Bug 1867431] Re: ERROR got an error from dpkg for pkg: 'libc6'

[Steve Langasek]

>From Jeffrey's log:

Preparing to unpack .../libcrypt1_1%3a4.4.10-10ubuntu1_amd64.deb ...
Unpacking libcrypt1:amd64 (1:4.4.10-10ubuntu1) ...
Setting up libcrypt1:amd64 (1:4.4.10-10ubuntu1) ...

Yes, this shows that you had the buggy libcrypt1 installed, which
satisfies the dependency of libc6 but has a problem that libc6 and
libcrypt1 don't agree on the path of libcrypt.so.1 in the dpkg database,
causing the Replaces: to go wrong and remove this file from disk.

Specifically, the old version of libcrypt1 considers
/usr/lib/$arch/libcrypt.so.1 to be the authoritative path of this file.
The new version of libcrypt1 has been fixed to match libc6, and consider
/lib/$arch/libcrypt.so.1 as the authoritative path of the file.  If your
system has usrmerge, then /lib is a symlink to /usr/lib on the
filesystem, so these paths resolve to the same thing, but dpkg doesn't
know it, so cannot correctly handle the upgrade.

The wrong path in libcrypt1 was resolved in libxcrypt
1:4.4.10-10ubuntu4, which is the version that just migrated to the
release pocket together with glibc 2.31.

Unfortunately, libxcrypt 1:4.4.10-10ubuntu1 somehow managed to make it
into the release pocket earlier (it shouldn't have, and I don't know
exactly how this happened), so some users already had it installed.  And
if they had this wrong version installed, libc6 does not force upgrade
to the fixed version of libcrypt1 first, so you still hit the bug.

After you've hit this problem, installing/reinstalling the *new* version
of libcrypt1 (1:4.4.10-10ubuntu4) should be enough to correct the
failure.

It will take some time to sort out an archive-side solution that would
prevent propagating this damage to more users of focal who had the buggy
libcrypt1 version installed.  At minimum it's going to require a
reupload of glibc with a bumped versioned dependency on libcrypt1, and
probably one of libxcrypt as well to manually handle the dpkg database
breakage.

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

Title:
  ERROR got an error from dpkg for pkg: 'libc6'

Status in glibc package in Ubuntu:
  Incomplete

Bug description:
  After the last upgrade I made this morning, at the error of dpkg on the libc6 package, I was no longer able to log in user: sudo apt update, full-upgrade or any login with "sudo", the message was "you have passed 3 attempts for wrong password ", at restart I tried to log in from the grub, recovery, I tried to click" repair package "with no result, not even to start a root shell was not successful, any attempt failed .
  Luckily before the update I took a snapshot with Timeshift on Btrfs, so I have the snapshot still saved in case it was used to reproduce the bug, I also have logs saved, since I have separate subvolumes.
  I enclose everything, if there are other details that can help you, I am available.
  Thank you

  log: https://paste.ubuntu.com/p/zSJcrYyW6H/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libc6 2.30-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 13:44:58 2020
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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