Comment # 12 on bug 1186781 from
According to the log messages by Yast, there were seven more packages installed
after the (ignored) failed installation of filesystem-15.5-40.2.x86_64 and
before the update was stopped by the broken system unable to execute any
binaries. The package glibc-2.33-6.13 was the next to last, which is probably
relevant because it provides the dynamic linker.

This looks like the system was actually broken by the installation of glibc on
an un-UsrMerged system. Most important question for me: do I have to expect
other issues than the broken symbolic links in /lib64 to the dynamic linker? I
still haven't rebooted the system and I'm concerned because I can't get root
access by starting su or sudo as argument of /usr/lib64/ld-2.33.so. I'm afraid
the answer to my question is positive because the location of other glibc
libraries on my system right now is also different from before the installation
according to the 'locate' utility.


You are receiving this mail because: