Fedora AppImage: `Error: libcurl-gnutls.so.4` and `Error: libcrypto.so.1.0.0`
See original GitHub issueThanks for what looks to be an awesome product. Unfortunately I cannot try it out because the AppImage doesn’t work on fedora 29.
hughest@argon [0] $ ./hokus-cms_linux_x86_64.AppImage
A JavaScript error occurred in the main process
Uncaught Exception:
Error: libcurl-gnutls.so.4: cannot open shared object file: No such file or directory
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:740:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:180:18)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
at Function.Module._load (internal/modules/cjs/loader.js:551:3)
at Module.require (internal/modules/cjs/loader.js:658:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object.<anonymous> (/tmp/.mount_hokus-gz2PkM/resources/app.asar/node_modules/nodegit/dist/nodegit.js:12:12)
at Object.<anonymous> (/tmp/.mount_hokus-gz2PkM/resources/app.asar/node_modules/nodegit/dist/nodegit.js:1145:3)
A temporary workaround for libcurl-gnutls.so.4
is
sudo ln -s /usr/lib64/libcurl.so.4 /usr/lib64/libcurl-gnutls.so.4
The we run into another error
hughest@argon [0] $ ./hokus-cms_linux_x86_64.AppImage
A JavaScript error occurred in the main process
Uncaught Exception:
Error: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:740:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:180:18)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:559:12)
at Function.Module._load (internal/modules/cjs/loader.js:551:3)
at Module.require (internal/modules/cjs/loader.js:658:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object.<anonymous> (/tmp/.mount_hokus-jmMm0s/resources/app.asar/node_modules/nodegit/dist/nodegit.js:12:12)
at Object.<anonymous> (/tmp/.mount_hokus-jmMm0s/resources/app.asar/node_modules/nodegit/dist/nodegit.js:1145:3)
Openssl 1.0.0 is no longer supported and should be considered a security issue if software depends on it. https://www.openssl.org/policies/releasestrat.html
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
error while loading shared libraries: libz.so: cannot open shared ...
Queries related to “error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory appimage”.
Read more >https://raw.githubusercontent.com/AppImage/pkg2app...
This is why we recommend oldstable # ingredients for AppImages apt ... lib/x86_64-linux-gnu/libssl.so.1.0.0: version `OPENSSL_1.0.2' not found (required by ...
Read more >Index of Unsupported Software - Gentoo Forums
Page:1 · "VPN Unlimited application: "VPN Protocol Connection Error"" Page:1 · "[SOLVED] libcurl.so.4: no version information available" Page:1 ...
Read more >ChangeLog.txt - SlackBuilds.org
... for version 20221201_2499ff2. system/clamav: Updated for version 1.0.0. ... for version 0.11.6. libraries/libcurl-gnutls: Patched to fix fatal error.
Read more >Comments - Mable & The Wood by Graffiti_Games - Itch.io
The error message tells me libcrypto.so.1.0.0 can not be found. ... to get libcrypto.so.1.0, as well as libcurl-gnutls for the error that came...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Quick update: This problem - in the next release - will go away because we are dropping NodeGit in favor of IsomorphicGit. I’ll let you know when this happen.
@bjmgeek , @timhughes - You should try the new release - 0.6.0. This issue probably was solved. Let me know if it worked for you.