After updating to the latest version of insomnia, I get a blank screen on startup, and the following error message in the DevTools panel:
Uncaught 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:173:20)
at Object.Module._extensions..node (module.js:598:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:187:18)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/tmp/.mount_insomnsplYYw/app/resources/app.asar/node_modules/insomnia-node-libcurl/lib/Easy.js:40:29)
at Object.<anonymous> (/tmp/.mount_insomnsplYYw/app/resources/app.asar/node_modules/insomnia-node-libcurl/lib/Easy.js:280:3)
Hmm, I have a feeling this is due to the latest version being built on Ubuntu Xenial. Going to revert back to the old version (Trusty) and try another release.
Workaround for other affected users:
sudo ln -s /usr/lib64/libcurl.so.4 /usr/lib64/libcurl-gnutls.so.4
Can you check if this is working now in v5.14.6?
https://github.com/getinsomnia/insomnia/releases/tag/v5.14.6
Hi 👋
I do have this issue with v5.14.3.
v5.14.6 is working perfectly ✅
It works, thank you!
Thanks!
I’m working around this by running bin_replace_string -r libcurl-gnutls.so.4 libcurl.so.4 node_modules/nodegit/build/Release/nodegit.node. I don’t want to create random symlinks in /usr/lib—that’s managed by my distro’s package manager.
EDIT: Oops, sorry for the bugspam, forgot that this isn’t the nodegit project xD.
@binki Since this seems to be the canonical location for this bug :P ...
I can't get ahold of bin_replace_string since it seems to be a gentoo package.
I tried this,
bbe -e 's/libcurl-gnutls.so.4/libcurl.so.4/' node_modules/nodegit/build/Release/nodegit.node > node_modules/nodegit/build/Release/nodegit.node
but unfortunately this is leading to a segfault.
Most helpful comment
Workaround for other affected users: