You have replaced the core system glibc with an custom version - I could not have foreseen such replacement.
Don’t blame that on me - I have nothing to do with that - I provided you with an unconditional removal of AUR packages - I have no means of knowing you have replaced vital system packages with custom packages.
And for the record - you have validated the list at the prompt
:: Do you want to remove these packages? [Y/n]
To restore functionality you will need to manually install the repo version when using a live ISO.
Based on your replacement of core system package with custom packages I will make a warning note.
How to do that? I can not use manjaro-chroot now as the log displayed.
Look, if you’ve got even a shred of a plausible guess or a practical solution, then spit it out now. Spare us the sarcastic nonsense – it’s just wasting our time.
You can still mount the root.
glibc is same version on all branches so
curl -O https://mirror.easyname.at/manjaro/pool/sync/glibc-2.41+r9+ga900dbaf70f0-1-x86_64.pkg.tar.zst
unpack the archive and manually copy the file to the mounted root
or use pacman pointing to the mounted root
sudo pacman -U glibc-2.41+r9+ga900dbaf70f0-1-x86_64.pkg.tar.zst --root /mnt
Thank you! I used your method to fix it, and now I can use manjaro-chroot.
@linux-aarhus Those previous errors are gone now. The earlier issues were probably caused by this glibc. Currently, I can enter the system using the previous kernel version. I thought that after manjaro-chroot stopped working, I’d have to reinstall the system. Thank you so much again!