Problems with libssl.so and libcrypto.so after 2022 Nov 5th updates

Hello there.

Environment:
$ uname -a
Linux flesh 5.15.77-1-lts #1 SMP Thu, 03 Nov 2022 17:26:01 +0000 x86_64 GNU/Linux

Symptoms: both emborg and megasync crash on launch after tofay 2022 Nov 5th updates:

`

$ emborg 2> err.log

`

emborg error: create:
Traceback (most recent call last):
File “/home/piero/.local/lib/python3.10/site-packages/borg/archiver.py”, line 38, in
from . import helpers
File “/home/piero/.local/lib/python3.10/site-packages/borg/helpers/init.py”, line 9, in
from .checks import * # NOQA
File “/home/piero/.local/lib/python3.10/site-packages/borg/helpers/checks.py”, line 4, in
from .errors import Error
File “/home/piero/.local/lib/python3.10/site-packages/borg/helpers/errors.py”, line 3, in
import borg.crypto.low_level
ImportError: libcrypto.so.1.1: cannot open shared object file: No such file or directory

`

$ megasync 2>> err.log

`

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

$ sudo pacman -Qs libcrypto.so
local/openssl 3.0.7-2
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security
$ sudo pacman -Qs libssl.so
local/openssl 3.0.7-2
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security

Solution: none

Patch: Due to libssl.so and libcrypto.so dependencies, I’ve temporarily ignored in /etc/pacman.conf:
IgnorePkg = lib32-openssl openssl libarchive sudo systemd

Of course, not happy at all with this.
Any suggestion, please?

Thanks in advance, Piero

Please refer to this existing Topic on this subject.

AUR packages?

If so, rebuild them and see if the issue is resolved.

1 Like

Yes, aur pacs.
Yes, already tried that, also yay… --rebuild and pacman -Suuyy as well.

No, I can live without *borg and Mega, but the problem with
libssl.so and libcrypto.so
Remains.

BTW, my workaround with IgnorePkg did not work because it breaks other libs.

So: btrfs snapshot back to yesterday, and no updates.

But this is not the solution, of course.

Any DIFFERENT hints, maybe?
:frowning:

Update: I’ve followed ricklinux suggestion to visit https://unix.stackexchange.com/questions/723616/how-to-fix-missing-libcrypto-so-1-1 :

The 3rd reply says that

… solution for me was to also install openssl-1.1 which provides libcrypto.so.1.1.

I can now confirm that yes: for me installing openssl-1.1 has fixed both my problems.

Thanks

3 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.