Running 1.22.0 AppImage on MX Linux

jcr.small started this chat 3 years ago

Hi there,

We heard of this once before. It's a system configuration issue.

If you search Google for "libcrypto.so.1.1 ubuntu" there are multiple solutions.

Let me know how you get on!

Remko

Replies (4)

R
Hi there,



We heard of this once before. It's a system configuration issue.



If you search Google for "libcrypto.so.1.1 ubuntu" there are multiple solutions.



Let me know how you get on!



Remko

1


J
Hi,
Just got this error when trying to run the AppImage:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Any help would be appreciated :)

1


J
Thanks for the hint Remko :)

OK for those that have a similar issue this is what I did to solve it:
Conditions: Running MX-Linux version MX-23_x64 - based on Debian Bookworm

1. Went to https://packages.debian.org/ (as my package manager did not have the required libssl1.1 package).
2. Searched for libssl1.1*
3. The last available version of this is for Debian Bullseye
4. Download the file libssl1.1_1.1.1n-0+deb11u5_amd64.deb (if you are running 64bit Linux)
5. Change to your Download directory and run the following command to install the package

sudo dpkg -i libssl1.1*.deb

1


C

In reply to jcr.small

Thanks for the hint Remko :) OK for those that have a similar issue this is what I did to solve it:...
Oh no, I see it is same issue. Apologies for repeating. One issue still: when I try to follow solution there and install latest libssl (it is v. 3.0.11 now I guess, not 1.1), then I get following error:



$ sudo dpkg -i libssl3_3.0.11-1deb12u2_amd64.deb
dpkg-deb: error: unexpected end of file in archive magic version number in libssl3_3.0.11-1
deb12u2_amd64.deb
dpkg: error processing archive libssl3_3.0.11-1deb12u2_amd64.deb (--install):
dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
libssl3_3.0.11-1
deb12u2_amd64.deb

Sorry if these are basic issues with easy workaround, I've looked up this error message and can't find solutions.

1