Update to glibc 2.31-0ubuntu5 breaks system

Bug #1867423 reported by xalt7x on 2020-03-14
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrade to this version I'm unable to login into system. Right after update
- I can't do anything with sudo. System immediately says that password is incorrect
$ sudo .
Sorry, try again.
Sorry, try again.
sudo: 3 incorrect password attempts
- GUI apps which require admin rights (synaptic) also stopped working
- After reboot SDDM can't reach login screen
- if you try recovery mode with root parameter system complains
/sbin/sulogin: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory

So after this update file
/usr/lib/x86_64-linux-gnu/libcrypt.so.1
got deleted.

On Kubuntu 20.04, which was last upgraded yesterday, upgrade stopped with some error about unfinished configuration of libcrypt1. On Ubuntu 20.04 (GNOME) which was last upgraded at Feb 16, upgrade went well but system also got broken.

Jarno Kaikkonen (jarnokai) wrote :

I can confirm I just ran the update as well and am facing the exact same problems now. System is unusable. Is it possible to copy in the necessary file from live USB? I need my system back up.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glibc (Ubuntu):
status: New → Confirmed
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1867423

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Jarno Kaikkonen (jarnokai) wrote :

I am sorry, but I can't reach a working terminal on the system, as I can't log in to any accounts, including root through recovery. Trying to log in to my own account from tty instantly says "Login incorrect" without even asking for the password, trying to access root shell from recovery complains about missing libcrypt.so.1. Login manager doesn't even launch.

xalt7x (xalt7x) wrote :

I managed to restore system (of course it's a temporary solution until libc6 package is fixed)

- boot from any debian-based live image or from parallel system
- gain access to disk with broken system
- sudo mount /dev/sda2 /mnt (where sda2 is a partition of your broken system)
- wget http://launchpadlibrarian.net/453587373/libc6_2.30-0ubuntu3_amd64.deb
- dpkg -x libc6_2.30-0ubuntu3_amd64.deb ~/libc6-previous
- sudo cp ~/libc6-previous/lib/x86_64-linux-gnu/libcrypt-2.30.so /mnt/lib/x86_64-linux-gnu/
- cd /mnt/lib/x86_64-linux-gnu/
- sudo ln -s libcrypt-2.30.so libcrypt.so.1

Now you can at least boot your system.

xalt7x (xalt7x) wrote :

@ Chris Guiver (guiverc)
I can't do that. "apport-collect" wants package glibc but this bug is for package libc6.

Jarno Kaikkonen (jarnokai) wrote :

I can confirm @ Evgen (xalt7x) 's solution of downloading libc and replacing the libcrypt library and adding the symbolic link - my system runs now.

xalt7x (xalt7x) wrote :

>>replacing the libcrypt library
Actually "adding" because both libcrypt-2.31.so and it's symbolic link (libcrypt.so.1) are just missing in this version.

Jarno Kaikkonen (jarnokai) wrote :

Oh, well. Anyways, after starting my system, running
sudo apt --fix-broken install
And updating the system has succesfully updated all my packages and after a restart the system still runs.

xalt7x (xalt7x) wrote :

I have faced another problem. Upgrade wasn't able to finish because
/usr/bin/perl: /lib64/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/bin/perl)
Solution was to remove libc6-amd64 as Debian upstream suggests (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951880). It's probably a different bug but connected to this since libcrypt-2.31.so was found in /lib64 .

Kamilion (kamilion) wrote :

Ran into this myself.

Last thing I saw in IRC was:
"I bet the affected users all had the bad libcrypt1 installed, from the day that it incorrectly migrated to the release pocket"

So, here's my wajig log of installations.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.