[SOLVED] error while loading shared libraries: libunistring.so.2

geoduck · 2022-11-26 13:39:28

I am a real newbie to Arch Linux. Today I was installing gdb, but when i finished it said that it misses some libraries libunistring... and so on. So I've found them on AUR and installed, but soon after it my pacman started saying: "pacman: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory". I briefly fixed it via "sudo cp /usr/lib/libunistring.so.5.0.0 /usr/lib/libunistring.so.2" , but are there any other possible solutions to this problem, which will "revert" the changes and what can i do with this gdb messages to make it work...

Thanks in advance

Last edited by geoduck (2022-11-26 16:18:18)

Trilby · 2022-11-26 13:51:07

First, don't do partial upgrades (which I'm 99.999% sure is what caused your problem).

Second, packages from the repos will never depend on an AUR package.

Third, never copy / symlink libraries. This doesn't fix problems, it just varnishes over them generally creating far worse problems.

Fourth, did I say, never do partial upgrades?

The first step in the fix is to fully upgrade your system and reinstall libunistring from the repos:

pacman -Syu
pacman --asdeps libunistring

Answer Y for yes when the second command asks if you want to replace libunistring-git.

Last edited by Trilby (2022-11-26 13:52:54)

geoduck · 2022-11-26 13:51:57

there is already something on this: https://bbs.archlinux.org/viewtopic.php?id=281295, but I don't find it very helpful

geoduck · 2022-11-26 13:58:45

I guess I should upgrade my system using live usb? cuz pacman is completely dead at the moment...

Scimmia · 2022-11-26 14:03:44

Or using pacman-static.

Trilby · 2022-11-26 14:22:50

I thought you said copying the library "briefly fixed it". Did the varnish wear off that quickly?

But yes, using a live usb (or pacman-static) would be the next step.

geoduck · 2022-11-26 14:32:28

varnish vanish...ed.

I'm sorry for making too much questions. I tried pacman-static (official prebuilt binary), but it ends with a question: "Import PGP key F296BDE50368C6CE, "T.J. Townsend <blakkheim@archlinux.org>"? [Y/n]", which i answer Y and then comes a minute of waiting and these errors:

error: key "F296BDE50368C6CE" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

I found wiki page, which suggests to regenerate keys via deleting /etc/pacman.d/gnupg and using pacman-key, so should I?

Scimmia · 2022-11-26 14:33:46

Update archlinux-keyring first.

geoduck · 2022-11-26 14:57:23

didn't help, still have the same minute (even like 5 minutes) to ponder about life and I still get errors about pgp key... so, "pacman-key" method or any other ideas?

Scimmia · 2022-11-26 15:01:42

There's no way you'd get that error with archlinux-keyring up-to-date.

geoduck · 2022-11-26 15:07:08

well, maybe it's something wrong with me, I run:

1) ./pacman-static -S archlinux-keyring
2) ./pacman-static -Syu
3) ...time passes...
4) errors. hey!!

geoduck · 2022-11-26 15:32:43

from what I've seen: in other cases this update (archlinux-keyring) makes something (always solves a problem actually), but in mine it just says that everything is up-to-date and reinstalls it...

maybe some advises..?

Last edited by geoduck (2022-11-26 15:36:26)

Slithery · 2022-11-26 15:47:21

You need to run...

./pacman-static -Sy archlinux-keyring
./pacman-static -Syu

This is the only time when using pacman -Sy <something> is acceptable because you are running a full update straight away afterwards.

geoduck · 2022-11-26 15:55:59

I made a small workaround, but idk how much it will help:

1) cp /usr/lib/libunistring.so.5 /usr/lib/libuinstring.so.2
2) pacman -S --asdeps libunistring
3) pacman -S archlinux-keyring
4) rm /usr/lib/libunistring.so.2
5) ./pacman-static -Syu (it worked somehow, because keys are new)
6) pacman is working it seems and update was successful

P.S. I've tried -Sy too (it didn't help)

let me reboot and check everything, and I'll close this topic

P.S.S. It helped, solved the problem and the subproblem (which is about gdb and valgrind).

Last edited by geoduck (2022-11-26 16:20:28)

geoduck · 2022-11-26 15:59:22

any ideas what I can try doing to test if its working alright?

(after full update gdb is working fine it seems, valgrind too)

Last edited by geoduck (2022-11-26 16:00:18)

geoduck · 2022-11-26 16:01:26

Slithery wrote:

This is the only time when using pacman -Sy <something> is acceptable because you are running a full update straight away afterwards.

Yeah, I understood that, but at that point I've already had the latest keyring as pacman said

Slithery · 2022-11-26 16:07:11

geoduck wrote:

Yeah, I understood that, but at that point I've already had the latest keyring as pacman said

No, you didn't. You just kept reinstalling the package that was already listed in your pacman database.

geoduck · 2022-11-26 16:14:53

Ok, won't argue here, because I am no one, but a newbie. That was my fault, so glad some of your suggestions helped.
I am closing this topic, everything seems to be working after reboot.
Thanks!

Trilby · 2022-11-26 16:46:46

geoduck wrote:

any ideas what I can try doing to test if its working alright?

If `pacman -Syu` runs without error, it'd seem all is well. You could also review the output of `pacman -Qkk` for good measure (looking particularly for altered files under /usr/lib), but I doubt that's particularly relevant now.

Last edited by Trilby (2022-11-26 16:47:35)

Arch Linux

#1 2022-11-26 13:39:28

[SOLVED] error while loading shared libraries: libunistring.so.2

#2 2022-11-26 13:51:07

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#3 2022-11-26 13:51:57

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#4 2022-11-26 13:58:45

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#5 2022-11-26 14:03:44

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#6 2022-11-26 14:22:50

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#7 2022-11-26 14:32:28

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#8 2022-11-26 14:33:46

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#9 2022-11-26 14:57:23

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#10 2022-11-26 15:01:42

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#11 2022-11-26 15:07:08

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#12 2022-11-26 15:32:43

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#13 2022-11-26 15:47:21

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#14 2022-11-26 15:55:59

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#15 2022-11-26 15:59:22

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#16 2022-11-26 16:01:26

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#17 2022-11-26 16:07:11

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#18 2022-11-26 16:14:53

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

#19 2022-11-26 16:46:46

Re: [SOLVED] error while loading shared libraries: libunistring.so.2

Board footer