Skip to main content
Topic: libpsl.so (Read 3370 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

libpsl.so

libpsl.so.5

Code: [Select]
pacman: error while loading shared libraries: libpsl.so.5: cannot open shared object file: No such file or directory

I know how to pacman -U previous pacman from cache but pacman does no longer work since last upgrade.
Am I the first to report this, is it only happening to me?  Doesn't anyone else update?  This was done about 20hrs ago or so but only realized it on next day's boot and run of pacman.


Re: libpsl.so

Reply #1
Code: [Select]
ln -s libpsl.so /usr/lib/libpsl.so.5

That should get pacman working for you to downgrade with pacman -U, after that run:
Code: [Select]
rm /usr/lib/libpsl.so.5
Chris Cromer

Re: libpsl.so

Reply #2
Is it directly related to pacman or is it from somewhere else?  In one installation networking is dead, which means the init system is not really starting networkmanager, as far as I can see.  Conky is producing the same error.

I wonder if I can port artools-chroot to void so I can fix things :P


Re: libpsl.so

Reply #3
Not directly related. pacman depends on curl, curl depends on libpsl. So you need to make sure libpsl and curl are updated correctly before you update pacman.
Chris Cromer

Re: libpsl.so

Reply #4
Ok, it seems to be working, but libpsl was also updated to 0.20 and I also have  (libpsl-0.19.1-1-x86_64.pkg.tar.xz) in cache.
Either the one or the other gives:

Code: [Select]
# pacman -Ql libpsl
libpsl /usr/
libpsl /usr/bin/
libpsl /usr/bin/psl
libpsl /usr/include/
libpsl /usr/include/libpsl.h
libpsl /usr/lib/
libpsl /usr/lib/libpsl.so
libpsl /usr/lib/libpsl.so.6
libpsl /usr/lib/libpsl.so.6.2.0
libpsl /usr/lib/pkgconfig/
libpsl /usr/lib/pkgconfig/libpsl.pc
libpsl /usr/share/
libpsl /usr/share/gtk-doc/
.
.
.

so maybe the error is in curl looking for so.5 instead of 6?

Re: libpsl.so

Reply #5
So, if I link this file to ...5 there should not be a reason to revert pacman to 19, 20 seems to be working fine with that link in place?
Or am I missing something?

Re: libpsl.so

Reply #6
The symlink is just a bandaid, it should not be left there. After you have everything upgraded try remove that symlink. If it still gives you that problem, let us know.
Chris Cromer

Re: libpsl.so

Reply #7
yes, as soon as I remove it anything that relies on curl --> libpsl breaks, including pacman.
I updated everything using the bandaid and left it in place.  Even if I reverted to previous pacman when I remove the link pacman is not working, so I upgraded again.

Re: libpsl.so

Reply #8
Could you try reinstalling curl. Please make sure you have the latest curl.
Chris Cromer

Re: libpsl.so

Reply #9
Aaahhhaaa!!

I only had one version of curl in cache, weird?  And when I tried reinstalling it pacman said the pkg was corrupt.
So I downloaded a new copy of the same and reinstalled it and the problem is gone!

How come curl looks like it was made 20180304 and I don't have an earlier copy?

Re: libpsl.so

Reply #10
4 installations down because of one corrupt pkg.
But what was it that made it corrupt I wonder, a previous version of curl labeled as the new one and not matching its own signature?

Re: libpsl.so

Reply #11
Curl needed to be rebuilt against the new libpsl. My guess is you had the curl from before the rebuild.
Chris Cromer

Re: libpsl.so

Reply #12
I installed the previous curl from system and the behavior was exactly the same. 
I guess it was an update in a bad moment ....  but in my cache I only had the one from gremlins which pacman considered as corrupt and I don't remove stuff from cache.  I have pkgs 5-6versions back and all installations share the same cache.

Thank you for the help but I did find this behavior a little strange.

Re: libpsl.so

Reply #13
I get this probel after  update system/libpsl from  0.19.1-1 to  0.20.0-1.
just follow what Chris suggest. Hope to be fixed soon.
Keep it Simple. Simple is Secure, Simple is Beautiful.

Re: libpsl.so

Reply #14
I just got this problem today & this solution worked wonders for me. I was convinced I might have to re-install Artix... O.o

It also makes NetworkManager stop functioning too, once the link is made NetworkManager works again, glad I didn't do all the updates on all my computers at once.