Aurelien Jarno <aurel...@aurel32.net> writes: > Hi, > > On 2022-09-26 09:45, Vasudev Kamath wrote: >> And post removing /usr/lib version of libc it seems to work fine and no >> crash is happening. >> >> └─(09:44:30 on master)──> expr >> >> 1 ↵ ──(Mon,Sep26)─┘ >> expr: missing operand >> Try 'expr --help' for more information. >> ┌─(~/.emacs.d)─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(vasudeva.sk@bhrigu:pts/8)─┐ >> └─(09:44:39 on master)──> > > Thanks for all the details. It's great that your system is now fixed. Do > you have an idea why libc6 2.34 ended up in /usr/lib/x86_64-linux-gnu? > I do not see any explanation from the glibc side. Did you attempt a > usrmerge migration that failed after moving some files, or do you think > it's unrelated? >
I seriously did not have a clue why system was in this state. I had installed system back in 2019 and just keep updating. Also it was not just glibc, a whole bunch of packages were in this state and it took me a while to fix the entire system. (Had to write script to automate entire process). I don't remember me attempting to install usrmerge but not sure if it came via some dependency and failed to install. Feels weird why system was in such a state. Cheers, Vasudev