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

[xfzv]

After updating openssl from 1.1.1.q-1 to 3.0.7-2 (testing repo), I'm getting the following error when running any paru command:

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

[ssleert]

try to build paru-git pkg)

[obj-obj]

@ssleert any rebuild fixes it, I just rebuilt the 1.11.1 release to fix it

[xfzv]

@ssleert I know, it was just a quick report 👍

[nalsai]

I was using the release build, which now doesn't work anymore due to this issue.

[Alsan]

I have the same exact problem after system upgrade. Then I install openssl-1.1 solved the problem.

ps: I'm using a variant of archlinux.

[zeertzjq]

Just re-running makepkg -si in the cloned directory with PKGBUILD (likely ~/.cache/paru/clone/paru/) fixes this. I think this is just how AUR packages work.

[Piqlet]

I have the same exact problem after system upgrade. Then I install openssl-1.1 solved the problem.

ps: I'm using a variant of archlinux.

me too fixed

sudo pacman -S openssl-1.1

[linnabraham]

I have the same exact problem after system upgrade. Then I install openssl-1.1 solved the problem.
ps: I'm using a variant of archlinux.

me too fixed

sudo pacman -S openssl-1.1

I'snt openssl 3.0.7 the latest version? Is this the recommended way then?

[ouuan]

Although rebuilding paru/paru-git or installing openssl-1.1 can fix this, I think we need a rebuild of paru-bin or a new release of paru.

[GlenMerlin]

I'snt openssl 3.0.7 the latest version? Is this the recommended way then?

It is the latest version but 1.1.1 is still supported until mid 2023 I believe. Only a few distros have jumped up to the 3.0 (for some reason there was no 2.0 version)

1.1.1 is not affected by the critical vulnerability that 3.0.0-3.0.6 is so this is currently a safe thing to do.

[m0xsec]

try to build paru-git pkg)

Following up to confirm that cloning paru-git from the AUR and running makepkg -si fixes the issue. If you previously had a different pre-built paru package installed, you will need to remove it as it will be in conflict with the paru-git package.

imo this is a better solution than installing a dated version of OpenSSL.

[Alsan]

I've check that multiple version of OpenSSL can be installed simultaneously, I have 3.0.7, 1.1.1.s-2, 1.0.2.u-1 installed in my system. The 1.0 is required by the WPS (an office suite application), 1.1 doesn't have any required by listed (and I don't have this version before this issue), the 3.0 is required by other packages required by the core. Therefore, 3.0 is the default in the system, and it could be a safe but might not be the recommended way to solve this issue.

I just wondering why paru is looking for the older version without a recompile.

[justinkb]

it's "looking for the older version" because it linked to libssl.so.1.1 and libcrypto.so.1.1 during build. it is a runtime dependency established at build time