Yesterday glibc was updated to vs 2.,26. This apparently caused problems.
This update deposits a file: /etc/nsswitch.conf.rpmnew. After the update has taken place and before any reboots, this file must be copied over nsswitch.conf, viz:
cd /etc
sudo mv nsswitch.conf nsswitch.conf.old
sudo mv nsswitch.conf.rpmnew nsswitch.conf
Here (1.3 KB) is the actual nsswitch.conf i.e the one provided by rpm, here (1.3 KB) is the old one, i.e. the one who causes the issue, and here (357 Bytes) is the diff. I added .txt extension to upload the files on this forum.
Blockquote-
rw-r–r-- 1 root root 1326 Sep 12 14:49 /etc/nsswitch.conf
-rw-r–r-- 1 root root 1326 Sep 12 14:49 /etc/nsswitch.conf.bak
-rw-r–r-- 1 root root 1337 Jul 16 09:14 /etc/nsswitch.conf.rpmsave
The contens of all the files are identical and are the one’s that cause the later version of glibc to fail.
Blockquote
This is after performing urpmi --auto-update
There was no libc in the update
Everything appears to be working
Did the update fail because there was already a backup file?
I know normally one doesn’t overwrite config files on update but in this circustance…?
This fix worked here on a computer that had had multiple boot attempts after the update. Obviously you have to access the broken system from ‘Live’ ISO or from another computer or another system if on a multi-boot computer to make the necessary adjustment.
@christopher_tanner I’m curious, how did you know to look for this? Is there some output in ‘urpmi --auto-update’ that tells us to look for a .rpmnew file or files?