Error while loading shared libraries: libcrypto.so.1.1

General system Newbie
1

I just tried to update my system and the konsole window auto-closed mid-update without providing any warning. When I try to repeat the update, I am given the following error:

sudo: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Running ls -l libcrypto* of my /usr/lib directory gives the following:

lrwxrwxrwx 1 root root 20 Aug 9 13:03 libcryptopp.so → libcryptopp.so.8.7.0
lrwxrwxrwx 1 root root 20 Aug 9 13:03 libcryptopp.so.8 → libcryptopp.so.8.7.0
-rwxr-xr-x 1 root root 4382736 Aug 9 13:03 libcryptopp.so.8.7.0
lrwxrwxrwx 1 root root 14 Nov 1 14:21 libcrypto.so → libcrypto.so.3
-r-xr-xr-x 1 root root 2828704 Jan 25 2020 libcrypto.so.1.0.0
-rwxr-xr-x 1 root root 4484080 Nov 1 14:21 libcrypto.so.3

I’m afraid to reboot into a failed update and I’m not sure what next to do.

I’m not sure what logs to provide, or what next to do. Thanks very much for any guidance.

-Barry

2

There was this thread with somewhat similar issue:

1 Like
3

I saw that, but it was a different error with a different libcrypto.so reference, so I was unsure it was applicable. Is it? If so, I’m going to need some assistance with implementing the solution.

4

I haven’t had this issue myself. Searching in Arch forum, there seems to be quite a few suggestions to resolve this.

One is to refresh the mirrors and try sudo pacman -Syyu to ensure that the system is not in a partial upgrade state.

You might want to try that first and see how it fares.

https://bbs.archlinux.org/search.php?search_id=1494902342

5

I’ve tried to update mirrors and sudo pacman -Syyu, but any command I issue with sudo is met with the same error. Does this mean I’ll need to chroot in to accomplish this? That strikes terror in my soul, but I’ll try if that’s what’s needed …

Thanks, @pebcak

1 Like
6

Well, this i a bit beyond my reach.
Honestly, I can’t tell if the issue can be resolved from the chroot. It might.

I would leave things as they are for the moment and wait for more competent users to chime in.
The upgrade to openssl 3.0.7-2 is apparently causing issues in some systems and most probably more information will be coming in on how to resolve it.

Sorry for not being of more help @bkaplan .

1 Like
7

mayby crypto++ is outdated ? also dont see any bond with openssl en crypto++ its a openssl issue atleast

8

openssl provides libcrypto.so:

$ pacman -Ql openssl | grep libcrypto
openssl /usr/lib/libcrypto.so
openssl /usr/lib/libcrypto.so.3
openssl /usr/lib/pkgconfig/libcrypto.pc

Apparently, here something has gone wrong since sudo is looking to load the older libcrypto.so.1.1.

$ pactree sudo | grep openssl 
├─openssl
│ │   │ │ └─openssl
│ │   │   └─openssl
├─openssl provides libcrypto.so=3-64
└─openssl provides libssl.so=3-64
1 Like
9

Seems this post has a solution?

10

Click me!
:computer_mouse:

11

It’s the multiverse. No way around it.

12

@bkaplan

What does it show?

sudo pacman -Syu
13

Any command that uses sudo results in the same error message:

sudo: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

14

Did you try installing openssl-1.1

Edit: Supposedly it provides libcrypto.so.1.1

15

His sudo is not working :wink:

16

Would need to download the tar package and update with pacman command?

17

It needs sudo, doesn’t it?

18

Not sure if pacman -U needs it? I’ve only used it a couple of times.

19

Of course it does. It needs to make changes to the system.

20

Okay then… sudo is screwed. :laughing: