[Bug 1867423] Re: Update to glibc 2.31-0ubuntu5 breaks system
Evgen
1867423 at bugs.launchpad.net
Sat Mar 14 12:46:05 UTC 2020
*** This bug is a duplicate of bug 1866844 ***
https://bugs.launchpad.net/bugs/1866844
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 .
** Bug watch added: Debian Bug tracker #951880
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951880
--
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/1867423
Title:
Update to glibc 2.31-0ubuntu5 breaks system
Status in glibc package in Ubuntu:
Confirmed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1867423/+subscriptions
More information about the foundations-bugs
mailing list