Re: [SOLVED] Glibc and filesystem update, I screwed it up

I wouldn't think that forgetting the lib32 version should do anything that terrible. After all, you might not have had multilib enabled at all.

Have you seen what is in /usr/lib64 and what owns it and its contents? The instructions said, I think, to update those packages first and then run the system upgrade. Have you tried that?

Note that in your output, it is trying to upgrade glibc but not filesystem which is not going to work. The instructions said to update the stuff with files in /usr/lib64 individually so I would try that.

Re: [SOLVED] Glibc and filesystem update, I screwed it up

cfr wrote:

Note that in your output, it is trying to upgrade glibc but not filesystem which is not going to work. The instructions said to update the stuff with files in /usr/lib64 individually so I would try that.

Yes, I've just noticed the same. I forgot the comma (or actually I did not remember I need to set it) in the --ignore command, so it should have looked like this:

pacman -Syu --ignore filesystem, glibc

Unfortunately the way I did it installed glibc nevertheless.

Shortly before doing the update I looked into the lib64 folder and saw its contents. Now it's been deleted of course and I can't start any application.

EDIT:Ok, I found libflashsupport.so in /usr/lib64/, since this probalbly belongs to the libflashsupport-oss AUR package I uninstalled the package. The file was still there, so I removed I manually.Although the lib64 directory is now empty I still can't update the filesystem I'm clueless... Shall I remove lib64 completely?

Re: [SOLVED] Glibc and filesystem update, I screwed it up

Sorry for the inconvenience. It's right, i have cinnamon installed and it seems that their repositories screwed something up. I'm sorry for you nuc my problem doesn't match yours and i doesn't know a solution for your problem...

EDIT:Ok, I found libflashsupport.so in /usr/lib64/, since this probalbly belongs to the libflashsupport-oss AUR package I uninstalled the package. The file was still there, so I removed I manually.Although the lib64 directory is now empty I still can't update the filesystem I'm clueless... Shall I remove lib64 completely?

Re: [SOLVED] Glibc and filesystem update, I screwed it up

Thanks for the tip cfr I will remember that. I checked the file on my other PC it file really belongs to libflashsupport-oss.

BTW - since I downgraded to glibc, everything works for me now and I can start my System without a live-CD.However I still can't update to the latest filesystem and glibc although /usr/lib64 is empty. Has nobody got a solution?

Re: [SOLVED] Glibc and filesystem update, I screwed it up

I have indeed already removed it. When I do pacman -Qo on libflashsupport.so, pacman says that this file doesn't belong to any package. It's really weird. It might be still bound to OSSv4 somehow because I also see libflashsupport.so in /lib64/oss/lib/. I will remove oss package and restart and see if it helped.

EDIT:I removed it but it didn't help. Then I just removed the whole /usr/lib64/ directory - and viola, I was able to update glibc and filesystem.

The only problem I got now, is that I can't reinstall libflashsupport-oss. Pacman's output:(conflict)libflashsupport-oss: /usr/lib/libflashsupport.so exists in filesystem. Could not update package.

UPDATE: Solved the issue by removing both OSS packages via pacman and then manually some leftovers. Reinstalling worked perfectly.