I was just messing up for my unreal-engine build which almost success just few files where getting error. And sorry for now i am unable to copy then due to current error the are like /usr/bin/../lib64 error a very big error .To fix this error i downloaded libc6, libc6-dev, linux-libc-dev-amd64 and all ubuntu 18 based deb files which i tried to install with sudo dpkg -i libc6.deb libc6-dev.dpkg linux-libc-dev.deb and me stupid thought that this command caused crash on the terminal so i just ran exit without thinking anything . and now each and every command gave error even sudo .The error is
relocation error: /usr/lib/libc.so.6: symbol _dl_fatal_printf version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time refrence
even my fish shell promt which i stole from gradua linux sucks giving same error for whoami and sed
plz help me out i can currently access my open apps which are brave, xfce4-terminal , thunar.
plz help me out as fast as possible i am really worried as nothing even sudo doesn’t work
first: sudo dpkg -i libc6.deb libc6-dev.dpkg linux-libc-dev.deb
that command wouldn’t even have begun to work with a standard installation - since dpkg is a different package manager than Arch/Manjaro’s pacman/pamac
You can install it however - and apparently you did.
Then you used it to install vital system files (glibc) - thereby very likely overwriting/messing up vital parts of your system.
With that Debian glibc it is not even to be expected that your system will still work, much less after now having a mix of original and “new” files due to your “stunt”
You could try to (probably focrfefully) reinstall the original glibc - which is likely still in your pacman cache (/var/cache/pacman/pkg/).
… if pacman still allows you to do that …
You could also try “surgery” from outside - boot a live system and use that to replace the files inside the package named glibc-2.xx.pkg.tar.zst (from your pacman cache).
it probably will - but it is not just one file
it is the contents of the package glibc-2.xx… as I said above
all of it
copy the files where pacman would put them when it was doing the installation …
no worries - they are still there
but since the system does not boot now, they are only accessible via booting from live medium - like the installer USB you would use to chroot …
or almost any other Linux live system