Incompatible version of openssl about gpgfrontend HOT 5 CLOSED

AppImages are indeed designed to bundle most of the dependencies required to run an application. However, they might still rely on some system libraries, especially if those libraries are expected to be present on all or most target systems. OpenSSL is often one such library because it provides cryptographic functionality that many systems already have installed. You can see the Related Issue here. In your case, the AppImage might be looking for OpenSSL 1.1.1, but can't find the 64-bit version installed on your system. The search path for shared libraries could be affecting this, as you mentioned.

As for the GpgFrontend, it's offering a Flatpak Version as a workaround. Flatpak packages are another form of software distribution that include all necessary libraries, providing a more controlled environment. Since you mentioned that they will formally introduce this in v2.1.2, trying out the Flatpak version could indeed be a viable solution to your environment issues.

from gpgfrontend.

qt.tlsbackend.ossl: Incompatible version of OpenSSL (built with OpenSSL 1.x, runtime version is >= 3.x)

It seems that GpgFrontend is built with OpenSSL 1.1.1 but the OpenSSL version on your machine is 3.x. Could you try to install OpenSSL 1.1.1? It may help.

from gpgfrontend.

I'm not downgrading the system's openssl two major versions to get this app to work. I'm just curious why an appimage would need to depend on a system's dynamic libraries. I thought they are packaged with everything needed to run?

from gpgfrontend.

Just did a quick check, and both 3.1.3 and 1.1.1 are installed on my system, however the 32-bit version of 1.1.1 is not.

from gpgfrontend.

Using the flatpak completely solved the problem!

from gpgfrontend.