Crash on Fedora 36 after got "Error: SSL connect error" when working with https websites #5088

trunglebka · 2022-08-17T03:01:24Z

ℹ️ Note from Insomnia team: We don't have a fix for this issue yet, but please refer to the workaround fix mentioned in ~~this comment~~ ~~(UPDATE) here~~.

SEE UPDATE 23 January 2023

Workaround

# remove existing insomnia installations
sudo dnf remove insomnia

# install latest insomnia
sudo dnf install https://github.com/Kong/insomnia/releases/download/core%402022.7.5/Insomnia.Core-2022.7.5.rpm

# download cups 2.4.1 libs and copy them to insomnia
curl -O https://kojipkgs.fedoraproject.org//packages/cups/2.4.1/7.fc36/x86_64/cups-libs-2.4.1-7.fc36.x86_64.rpm
rpm2cpio cups-libs-2.4.1-7.fc36.x86_64.rpm | cpio -idmv
sudo cp ./usr/lib64/libcups* /opt/Insomnia/.

# run insomnia
insomnia

Expected Behavior

Working normally

Actual Behavior

After sending a request to a https website like https://google.com, got an error: Error: SSL connect error

Reproduction Steps

Send request to any https website. E.g. https://google.com
Send request again (any https)
App crash

Is there an existing issue for this?

I have searched the issue tracker for this problem.

Additional Information

Timeline:

* Preparing request to https://google.com/
* Current time is 2022-08-17T02:41:53.423Z
* Enable automatic URL encoding
* Using default HTTP version
* Enable SSL validation
*   Trying 172.217.24.110:443...
* Connected to google.com (172.217.24.110) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS alert, internal error (592):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to google.com:443 
* Closing connection 0

Log from console:

(base) ➜  ~ /opt/Insomnia/insomnia
09:41:43.262 › Running version 2022.5.0
09:41:43.271 › [electron client protocol] FAILED to set default protocol 'insomnia://'
09:41:43.278 › [electron client protocol] the current executable is not the default protocol for 'insomnia://'
09:41:43.305 › [electron client protocol] the default application set for 'insomnia://' is 'insomnia.desktop
'
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
09:41:43.422 › [fix] Running database repairs
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open nvidia-drm: /usr/lib64/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: nvidia-drm
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load swrast driver
09:41:43.890 › [db] Initialized DB at /home/chicky/.config/Insomnia/insomnia.$TYPE.db
09:41:43.890 › [db] Init responses DB
09:41:43.892 › [localstorage] Initialized at /home/chicky/.config/Insomnia/localStorage
09:41:43.955 › [main] Loading file:///opt/Insomnia/resources/app.asar/index.html
09:41:44.464 › [updater] Updater not running platform=linux dev=false
[0817/094201.253776:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0817/094201.254021:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0817/094201.254161:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1]    18463 segmentation fault (core dumped)  /opt/Insomnia/insomnia

Insomnia Version

2022.5.0 and later

What operating system are you using?

Other Linux

Operating System Version

Fedora 36 and 37

Installation method

rpm

Last Known Working Insomnia version

No response

The text was updated successfully, but these errors were encountered:

wongstein · 2022-08-17T12:55:40Z

First, have you tried unchecking validate certificates in your preferences:

Second (if the unchecking the certificates doesn't work), can you reproduce an error with curl? You can get the curl command from Insomnia by clicking on the drop down button next to your saved request

Then click on "copy as curl" from the drop down menu:

And paste that into your terminal window

trunglebka · 2022-08-17T13:11:47Z

First: Yes, I tried unchecking validate certificates. But since my OS is the recent Fedora version (36) with latest updated packages and google is a very popular website I don't think that there is a problem with Certificate/CA. This is timeline with SSL validation disabled

* Preparing request to https://google.com/
* Current time is 2022-08-18T01:31:00.965Z
* Enable automatic URL encoding
* Using default HTTP version
* Disable SSL validation
*   Trying 142.250.66.78:443...
* Connected to google.com (142.250.66.78) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS alert, internal error (592):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to google.com:443 
* Closing connection 0

Second: Yes, I tried both cURL, Postman (installed after so many tries to use Insomnia without success, including downgrade to 2022.4.0) and of course browser - all work flawlessly. This is verbose log of cURL

➜  ~ curl -v --request GET \
  --url https://google.com/
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 142.250.204.142:443...
* Connected to google.com (142.250.204.142) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.google.com
*  start date: Jul 18 08:18:57 2022 GMT
*  expire date: Oct 10 08:18:56 2022 GMT
*  subjectAltName: host "google.com" matched cert's "google.com"
*  issuer: C=US; O=Google Trust Services LLC; CN=GTS CA 1C3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: google.com]
* h2h3 [user-agent: curl/7.82.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x562964dc13f0)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/2
> Host: google.com
> user-agent: curl/7.82.0
> accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 301 
< location: https://www.google.com/
< content-type: text/html; charset=UTF-8
< date: Thu, 18 Aug 2022 01:35:10 GMT
< expires: Sat, 17 Sep 2022 01:35:10 GMT
< cache-control: public, max-age=2592000
< server: gws
< content-length: 220
< x-xss-protection: 0
< x-frame-options: SAMEORIGIN
< alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
< 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="https://www.google.com/">here</A>.
</BODY></HTML>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection #0 to host google.com left intact

Rayvion · 2022-08-18T05:18:38Z

I have the exact same problem on Fedora 36 after a system update since tuesday.
Crash is with Error "Speicherzugriffsfehler" => german translation of a segfault.

Was on version 2022.3.0 as this started and upgraded to 2022.5.0 and also tried 2022.6.0 beta, no difference at all.
No SSL errors in any other program that i'm aware of.

Core dump on crash:

Process 9292 (insomnia) of user ##### dumped core.

Module /tmp/.org.chromium.Chromium.hOplDp with build-id 1fdd3631cb501b327b45531b6ee85a0aa9cbe6bb
Metadata for module /tmp/.org.chromium.Chromium.hOplDp owned by FDO found: {
       "type" : "rpm",
       "name" : "opensc",
       "version" : "0.22.0-6.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module linux-vdso.so.1 with build-id 26f3e7f0c7154e781438e7920d9994ce30eb9230
Module libnss_resolve.so.2 with build-id 6e24ab4f3bcd2120fdda86393ebe4ddfc82d68ed
Metadata for module libnss_resolve.so.2 owned by FDO found: {
       "type" : "rpm",
       "name" : "systemd",
       "version" : "250.8-1.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libnss_mdns4_minimal.so.2 with build-id fe461d55e34f82892fff98869493b1faba410e52
Metadata for module libnss_mdns4_minimal.so.2 owned by FDO found: {
       "type" : "rpm",
       "name" : "nss-mdns",
       "version" : "0.15.1-5.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libnss_myhostname.so.2 with build-id c17f102a94b4e71d9dde194419f609849e97fbfd
Metadata for module libnss_myhostname.so.2 owned by FDO found: {
       "type" : "rpm",
       "name" : "systemd",
       "version" : "250.8-1.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libpcsclite.so.1 with build-id 6f44b6779cb46fe0cf3dae084d9a931f9f250658
Metadata for module libpcsclite.so.1 owned by FDO found: {
       "type" : "rpm",
       "name" : "pcsc-lite",
       "version" : "1.9.8-1.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libopensc.so.8 with build-id 99ba126a7317a9e3a2a474a4dd030018c07dd224
Metadata for module libopensc.so.8 owned by FDO found: {
       "type" : "rpm",
       "name" : "opensc",
       "version" : "0.22.0-6.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module opensc-pkcs11.so with build-id 7b401f1b5992dd2c9386242164e9195b04894e40
Metadata for module opensc-pkcs11.so owned by FDO found: {
       "type" : "rpm",
       "name" : "opensc",
       "version" : "0.22.0-6.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module p11-kit-trust.so with build-id e8fad97f56aec95b74768777c51d757920ac956c
Metadata for module p11-kit-trust.so owned by FDO found: {
       "type" : "rpm",
       "name" : "p11-kit",
       "version" : "0.24.1-2.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libfreeblpriv3.so with build-id 229985045b01833ed9e291d36f1b9e1fbf99f15e
Module libsoftokn3.so with build-id e3aa28a3f19e11750367d2f493db8795adcd5147
Module libudev.so.1 with build-id 002cce667c466b2f92130c99f55d21afa5669636
Metadata for module libudev.so.1 owned by FDO found: {
       "type" : "rpm",
       "name" : "systemd",
       "version" : "250.8-1.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libdconfsettings.so with build-id bbf80c3788c9b836a1ae22bd23e75712368ce187
Metadata for module libdconfsettings.so owned by FDO found: {
       "type" : "rpm",
       "name" : "dconf",
       "version" : "0.40.0-6.fc36",
       "architecture" : "x86_64",
       "osCpe" : "cpe:/o:fedoraproject:fedora:36"
}

Module libpk-gtk-module.so with build-id f9085fc07471c5b410ff6a64c1ca25e557f90458
Stack trace of thread 9292:
#0  0x0000557c873b8dd7 n/a (insomnia + 0x4ecadd7)
#1  0x00007f8997a52a9e err_delete_thread_state (libcrypto.so.3 + 0x16ba9e)
#2  0x00007f8997a98014 init_thread_stop.part.0 (libcrypto.so.3 + 0x1b1014)
#3  0x00007f8997a9d541 OPENSSL_thread_stop (libcrypto.so.3 + 0x1b6541)
#4  0x00007f8997a9d5a5 OPENSSL_cleanup (libcrypto.so.3 + 0x1b65a5)
#5  0x00007f8998b42085 __run_exit_handlers (libc.so.6 + 0x41085)
#6  0x00007f8998b42200 exit (libc.so.6 + 0x41200)
#7  0x00007f8998b2a557 __libc_start_call_main (libc.so.6 + 0x29557)
#8  0x00007f8998b2a609 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x29609)
#9  0x0000557c841e9baa _start (insomnia + 0x1cfbbaa)

Stack trace of thread 9293:
#0  0x00007f8998c0688f __poll (libc.so.6 + 0x10588f)
#1  0x0000557c86b4985f n/a (insomnia + 0x465b85f)
#2  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#3  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#4  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9299:
#0  0x00007f8998bddbdf wait4 (libc.so.6 + 0xdcbdf)
#1  0x0000557c873a9af4 n/a (insomnia + 0x4ebbaf4)
#2  0x0000557c873a73b0 n/a (insomnia + 0x4eb93b0)
#3  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9304:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c873aac03 n/a (insomnia + 0x4ebcc03)
#3  0x0000557c873ab3bf n/a (insomnia + 0x4ebd3bf)
#4  0x0000557c873ab14e n/a (insomnia + 0x4ebd14e)
#5  0x0000557c8731efbd n/a (insomnia + 0x4e30fbd)
#6  0x0000557c87372624 n/a (insomnia + 0x4e84624)
#7  0x0000557c8733d102 n/a (insomnia + 0x4e4f102)
#8  0x0000557c8738bb08 n/a (insomnia + 0x4e9db08)
#9  0x0000557c8738bc72 n/a (insomnia + 0x4e9dc72)
#10 0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#11 0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#12 0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9305:
#0  0x00007f8998c1278e epoll_wait (libc.so.6 + 0x11178e)
#1  0x0000557c84567e39 n/a (insomnia + 0x2079e39)
#2  0x0000557c84559772 uv_run (insomnia + 0x206b772)
#3  0x0000557c8ac47eb1 n/a (insomnia + 0x8759eb1)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9311:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c84555ee8 n/a (insomnia + 0x2067ee8)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9308:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c8ac48062 n/a (insomnia + 0x875a062)
#4  0x0000557c8ac45c12 n/a (insomnia + 0x8757c12)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9312:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c84555ee8 n/a (insomnia + 0x2067ee8)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9420:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c873aac03 n/a (insomnia + 0x4ebcc03)
#3  0x0000557c873ab3bf n/a (insomnia + 0x4ebd3bf)
#4  0x0000557c873854ae n/a (insomnia + 0x4e974ae)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385aad n/a (insomnia + 0x4e97aad)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9309:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b95c50 __new_sem_wait_slow64.constprop.0 (libc.so.6 + 0x94c50)
#2  0x0000557c845650d0 uv_sem_wait (insomnia + 0x20770d0)
#3  0x0000557c8acc211d n/a (insomnia + 0x87d411d)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9422:
#0  0x00007f8998bd95b5 clock_nanosleep@GLIBC_2.2.5 (libc.so.6 + 0xd85b5)
#1  0x00007f8998bdde27 __nanosleep (libc.so.6 + 0xdce27)
#2  0x00007f8998bddd5e sleep (libc.so.6 + 0xdcd5e)
#3  0x0000557c846c6bc7 n/a (insomnia + 0x21d8bc7)
#4  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9426:
#0  0x00007f8998c0688f __poll (libc.so.6 + 0x10588f)
#1  0x0000557c873b1688 n/a (insomnia + 0x4ec3688)
#2  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#3  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#4  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9313:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c84555ee8 n/a (insomnia + 0x2067ee8)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9310:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c84555ee8 n/a (insomnia + 0x2067ee8)
#4  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#5  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9556:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385c06 n/a (insomnia + 0x4e97c06)
#6  0x0000557c87385a7d n/a (insomnia + 0x4e97a7d)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9307:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c8ac48062 n/a (insomnia + 0x875a062)
#4  0x0000557c8ac45c12 n/a (insomnia + 0x8757c12)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9427:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385add n/a (insomnia + 0x4e97add)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9417:
#0  0x00007f8998c0688f __poll (libc.so.6 + 0x10588f)
#1  0x00007f899a13923d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa23d)
#2  0x00007f899a0e1940 g_main_context_iteration (libglib-2.0.so.0 + 0x52940)
#3  0x00007f899a0e1991 glib_worker_main (libglib-2.0.so.0 + 0x52991)
#4  0x00007f899a10e302 g_thread_proxy (libglib-2.0.so.0 + 0x7f302)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9552:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385a7d n/a (insomnia + 0x4e97a7d)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9418:
#0  0x00007f8998c0688f __poll (libc.so.6 + 0x10588f)
#1  0x00007f899a13923d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa23d)
#2  0x00007f899a0e36cf g_main_loop_run (libglib-2.0.so.0 + 0x546cf)
#3  0x00007f8999fc6ada gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x114ada)
#4  0x00007f899a10e302 g_thread_proxy (libglib-2.0.so.0 + 0x7f302)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9424:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385a7d n/a (insomnia + 0x4e97a7d)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9306:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d210 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x8c210)
#2  0x0000557c84565289 uv_cond_wait (insomnia + 0x2077289)
#3  0x0000557c8ac48062 n/a (insomnia + 0x875a062)
#4  0x0000557c8ac45c12 n/a (insomnia + 0x8757c12)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9423:
#0  0x00007f8998c0688f __poll (libc.so.6 + 0x10588f)
#1  0x00007f899a13923d g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa23d)
#2  0x00007f899a0e1940 g_main_context_iteration (libglib-2.0.so.0 + 0x52940)
#3  0x00007f897c2e73ad dconf_gdbus_worker_thread (libdconfsettings.so + 0x73ad)
#4  0x00007f899a10e302 g_thread_proxy (libglib-2.0.so.0 + 0x7f302)
#5  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#6  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9469:
#0  0x00007f8998c1278e epoll_wait (libc.so.6 + 0x11178e)
#1  0x0000557c874ce9da n/a (insomnia + 0x4fe09da)
#2  0x0000557c874cc51b n/a (insomnia + 0x4fde51b)
#3  0x0000557c873bbcf2 n/a (insomnia + 0x4ecdcf2)
#4  0x0000557c87372624 n/a (insomnia + 0x4e84624)
#5  0x0000557c8733d102 n/a (insomnia + 0x4e4f102)
#6  0x0000557c8738bb08 n/a (insomnia + 0x4e9db08)
#7  0x0000557c8738bc72 n/a (insomnia + 0x4e9dc72)
#8  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#9  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#10 0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9434:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385aad n/a (insomnia + 0x4e97aad)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)

Stack trace of thread 9551:
#0  0x00007f8998b8aa19 __futex_abstimed_wait_common (libc.so.6 + 0x89a19)
#1  0x00007f8998b8d504 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8c504)
#2  0x0000557c873aad46 n/a (insomnia + 0x4ebcd46)
#3  0x0000557c873ab390 n/a (insomnia + 0x4ebd390)
#4  0x0000557c87385472 n/a (insomnia + 0x4e97472)
#5  0x0000557c87385e32 n/a (insomnia + 0x4e97e32)
#6  0x0000557c87385a7d n/a (insomnia + 0x4e97a7d)
#7  0x0000557c873ae6a0 n/a (insomnia + 0x4ec06a0)
#8  0x00007f8998b8de2d start_thread (libc.so.6 + 0x8ce2d)
#9  0x00007f8998c131b0 __clone3 (libc.so.6 + 0x1121b0)
ELF object binary architecture: AMD x86-64

davelima · 2022-08-18T15:28:58Z

Same here. Same results on 2022.4.0 and 2022.5.1

vavsab · 2022-08-19T13:31:15Z

Same behavior on Fedora 26

neo-donnie-walsh · 2022-08-19T16:49:42Z

I have been facing this issue for a little while as well, after updating my system a few days ago on f36

davelima · 2022-08-23T14:36:49Z

Could be this related to #4543 ?

I have tried the workaround described in this comment but got no luck.

sarim · 2022-08-23T15:42:23Z

The provided rpm is using gnutls. ldd shows libgnutls.so.30. No libssl. So it makes sense your openssl workaround didn't have any effect. @davelima

zLupa · 2022-08-24T00:18:48Z

Having the same error on fedora 36.
On the first request, it fails with "Error: SSL connect error" and on the second request it just crashes

Nopraz · 2022-08-24T14:04:48Z

Hello, same problem for me on fedora 36 on 2022.4.0, 2022.4.2, 2022.5.0 and 2022.5.1
Insomnia gives me a segmentation fault error

octaviobarbosa · 2022-08-25T15:28:08Z

Hey! same problem here on Fedora 36.

Please for God's sake help me... I can't keep working on postman. I need my Insomnia back 😭😭

AlenBenkovic · 2022-08-26T10:34:11Z

Same problem here with Insomnia 2022.5.1 and F36

filfreire · 2022-08-26T11:57:20Z

Hi folks, just a quick update, we're aware of this issue and we know it's affecting a handful of users, we'll be looking into it as soon as possible. Please bear with us and if it helps in your case, I recommend using an older stable version, perhaps 2022.4.2.

EDIT: I just noticed @Nopraz comment that 2022.4.2 might not work, so it could be be some change we've introduced earlier. Please ping me here if you are using a version that works for Fedora 36, what is the version number.

Heads up @subnetmarco @wongstein - tracking this one internally in https://linear.app/insomnia/issue/INS-1827/community-bug-crash-on-fedora-36-after-got-error-ssl-connect-error

davelima · 2022-08-26T15:34:12Z

@filfreire thanks!

I have made some tests with older versions and it all seems to have the same issue, so i've reviewed the last updates on my OS and looks like the problem starts happening after upgrade cups from 2.4.1 to 2.4.2 (why i cannot say).

Downgrading cups to 2.4.1 solves the problem. Hope that piece of info help you guys.

This is the list of downgraded packages:

cups-1:2.4.1-7.fc36.x86_64
cups-client-1:2.4.1-7.fc36.x86_64
cups-filesystem-1:2.4.1-7.fc36.noarch
cups-ipptool-1:2.4.1-7.fc36.x86_64
cups-libs-1:2.4.1-7.fc36.x86_64

EDIT:
There was actually some SSL related changes on cups 2.4.2, according to the changelog

bisby · 2022-08-26T15:41:02Z

Downgrading insomnia to 2022.4.2 didn't work.

Downgrading cups to 2.4.1 did work.

sudo dnf install cups-1:2.4.1-7.fc36.x86_64 properly downgraded all 5 packages in 1 go.

EDIT: I'm just confirming that @davelima was right about cups. He did all the investigative work and is the real MVP.

neo-donnie-walsh · 2022-08-26T16:19:59Z

Downgrading insomnia to 2022.4.2 didn't work.

Downgrading cups to 2.4.1 did work.

sudo dnf install cups-1:2.4.1-7.fc36.x86_64 properly downgraded all 5 packages in 1 go.

This worked for me. You are my hero.

octaviobarbosa · 2022-08-26T17:49:58Z

Downgrading insomnia to 2022.4.2 didn't work.

Downgrading cups to 2.4.1 did work.

sudo dnf install cups-1:2.4.1-7.fc36.x86_64 properly downgraded all 5 packages in 1 go.

MY HERO!

thanks!

fhdiaze · 2022-08-26T19:18:44Z

It worked for me also. Thanks.

sarim · 2022-08-26T21:06:55Z

I only had cups-libs installed. So I just downgraded it, sudo dnf install cups-libs-1:2.4.1-7.fc36. It seems to be working now.

Nopraz · 2022-08-29T08:32:23Z

Downgrading insomnia to 2022.4.2 didn't work.

Downgrading cups to 2.4.1 did work.

sudo dnf install cups-1:2.4.1-7.fc36.x86_64 properly downgraded all 5 packages in 1 go.

EDIT: I'm just confirming that @davelima was right about cups. He did all the investigative work and is the real MVP.

Thank you so much !

But why does Insomnia uses cups ? Isn't cups for printers ?

filfreire · 2022-08-29T13:50:41Z

Hi folks, quick update, but after installing updates on Fedora 36, I can reproduce the exact same issue, with these error logs

[0829/144040.857270:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0829/144040.858037:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0829/144040.858396:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0829/144040.864807:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0829/144040.864852:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Segmentation fault (core dumped)

and Insomnia crashing soon after the SSL error:

Solution

I tried solution mentioned above by @davelima and @bisby

And after running sudo dnf install cups-1:2.4.1-7.fc36.x86_64 it's back working:

Thank you @davelima and @bisby 😉🎖️

looks like the problem starts happening after upgrade cups from 2.4.1 to 2.4.2 (why i cannot say).

This is the part where I also have no idea at the moment. Tagging @DMarby and @johnwchadwick, perhaps they might have a hint here.

vicenterusso · 2022-08-30T13:34:57Z

Just to reinforce sudo dnf install cups-1:2.4.1-7.fc36.x86_64 did fixed the same error after F36 system upgrade. First SSL Error, then a crash.

Valeu @davelima

sarim · 2022-09-02T19:01:33Z

So I compiled libcurl against my system's installed libcurl. I wasn't happy with cups downgrade workaround. I used the following steps

make sure dependencies are installed

sudo dnf install libcurl-devel make automake gcc gcc-c++

git clone --depth 1 --branch core@2022.5.1 https://github.com/Kong/insomnia
cd insomnia

nvm exec npm run bootstrap

## these env are probably not needed
export npm_config_runtime=electron
export npm_config_target=v19.0.3
export npm_config_build_from_source=true
export npm_config_node_libcurl_cpp_std=c++17
export npm_config_disturl=https://electronjs.org/headers
##

Edit packages/insomnia/electron-builder.config.js and add buildDependenciesFromSource: true. This config actually makes packages app's libcurl to be recompiled.

nvm exec npm run app-package
sudo dnf localinstall packages/insomnia/dist/Insomnia.Core-2022.5.1.rpm

Now its working fine with latest cups installed.

darkguy2008 · 2022-09-05T06:21:38Z

Thanks @sarim for the detailed writeup! I would've never been able to compile Insomnia otherwise. This took ages to build on my i5 12400, but in the end it worked. Fedora 36 as well. I didn't like the idea of downgrading the cups-lib package, nor removing it as others suggested - it wanted to remove all of my installed packages, quite crazy.

This is something that the Insomnia team should really look into ASAP, it's basically making the app unusable in Fedora 36. If your instructions worked for recompiling the app and making it work - couldn't the Insomnia team replicate this and make an updated version?

Also, does anybody know if the same issue happens with the AppImage?

Thanks!

sarim · 2022-09-05T14:59:02Z

Also, does anybody know if the same issue happens with the AppImage?

Yes, issue also happens with the official provided AppImage. You can use the AppImage after compiling from my instructions. It'll be in packages/insomnia/dist directory.

If your instructions worked for recompiling the app and making it work - couldn't the Insomnia team replicate this and make an updated version?

I don't know the metric of user distro's, who are the audience of rpm packages? Fedora users? centos/almalinux? suse?. Instead of trying to make a single rpm work in all distro/all version, A simple fix could be just to publish separate packages for fc35/fc36. It could be easily done with modifying existing github actions a little bit. I can do a PR if that direction is acceptable to insomnia team.

ckujau · 2022-12-09T10:10:57Z

Hi folks, while we don't have a more definitive solution, in order to unblock you in the meantime, I've compiled an experimental build on my fork which you can download and use:

While this works on this Fedora 37 installation (thank you!), the following happens during installation beause a Slack installation seems to be in the way:

$ sudo dnf install https://github.com/filfreire/insomnia/releases/download/fedora-experiment%408ae4fe71/Insomnia.Core-2022.7.0-beta.5-fedora.rpm

Error: Transaction test error:
  file /usr/lib/.build-id/0d/9fad3f21b1e381cc66b5efcae8f3910ae0edc1 from install of insomnia-2022.7.0_beta.5-1.x86_64 conflicts with file from package slack-4.29.149-0.1.el8.x86_64
  file /usr/lib/.build-id/76/9d0269491ca2313fcd15d63059bac67bd8b1b3 from install of insomnia-2022.7.0_beta.5-1.x86_64 conflicts with file from package slack-4.29.149-0.1.el8.x86_64
  file /usr/lib/.build-id/c2/dcac7cb6a727685d10d4161a0d14988f12a0fa from install of insomnia-2022.7.0_beta.5-1.x86_64 conflicts with file from package slack-4.29.149-0.1.el8.x86_64
  file /usr/lib/.build-id/cb/dc9db5fec0e6129bddcb0c282be98be4c6966e from install of insomnia-2022.7.0_beta.5-1.x86_64 conflicts with file from package slack-4.29.149-0.1.el8.x86_64

$ ls -l /usr/lib/.build-id/{0d/9fad3f21b1e381cc66b5efcae8f3910ae0edc1,76/9d0269491ca2313fcd15d63059bac67bd8b1b3,c2/dcac7cb6a727685d10d4161a0d14988f12a0fa,cb/dc9db5fec0e6129bddcb0c282be98be4c6966e}
lrwxrwxrwx. 1 root root 40 Nov  7 22:28 /usr/lib/.build-id/0d/9fad3f21b1e381cc66b5efcae8f3910ae0edc1 -> ../../../../usr/lib/slack/libvulkan.so.1
lrwxrwxrwx. 1 root root 38 Nov  7 22:28 /usr/lib/.build-id/76/9d0269491ca2313fcd15d63059bac67bd8b1b3 -> ../../../../usr/lib/slack/libffmpeg.so
lrwxrwxrwx. 1 root root 35 Nov  7 22:28 /usr/lib/.build-id/c2/dcac7cb6a727685d10d4161a0d14988f12a0fa -> ../../../../usr/lib/slack/libEGL.so
lrwxrwxrwx. 1 root root 40 Nov  7 22:28 /usr/lib/.build-id/cb/dc9db5fec0e6129bddcb0c282be98be4c6966e -> ../../../../usr/lib/slack/chrome-sandbox

Removing these symlinks did not help, but forcefully installing the package did:

$ wget https://github.com/filfreire/insomnia/releases/download/fedora-experiment%408ae4fe71/Insomnia.Core-2022.7.0-beta.5-fedora.rpm
$ sudo rpm -hiv --force Insomnia.Core-2022.7.0-beta.5-fedora.rpm

$ ls -l /usr/lib/.build-id/{0d/9fad3f21b1e381cc66b5efcae8f3910ae0edc1,76/9d0269491ca2313fcd15d63059bac67bd8b1b3,c2/dcac7cb6a727685d10d4161a0d14988f12a0fa,cb/dc9db5fec0e6129bddcb0c282be98be4c6966e}
lrwxrwxrwx. 1 root root 39 Nov 24 17:15 /usr/lib/.build-id/0d/9fad3f21b1e381cc66b5efcae8f3910ae0edc1 -> ../../../../opt/Insomnia/libvulkan.so.1
lrwxrwxrwx. 1 root root 37 Nov 24 17:15 /usr/lib/.build-id/76/9d0269491ca2313fcd15d63059bac67bd8b1b3 -> ../../../../opt/Insomnia/libffmpeg.so
lrwxrwxrwx. 1 root root 34 Nov 24 17:15 /usr/lib/.build-id/c2/dcac7cb6a727685d10d4161a0d14988f12a0fa -> ../../../../opt/Insomnia/libEGL.so
lrwxrwxrwx. 1 root root 39 Nov 24 17:15 /usr/lib/.build-id/cb/dc9db5fec0e6129bddcb0c282be98be4c6966e -> ../../../../opt/Insomnia/chrome-sandbox

darkguy2008 · 2022-12-23T03:55:48Z

@filfreire are there any news regarding this experimental build? I'm getting the same thing in Fedora 37 with 2022.7.

@CrystalSpore what other tool are you using? I'm really having a hard time trying to use Insomnia under Fedora and Postman isn't exactly my cup of tea.

@padys thanks for the workaround, unfortunately it didn't work for me with Fedora 37 and Insomnia 2022.7 or 2022.6 :(

I'm currently needing to share requests now with other people I work with and I was thinking in getting a team subscription, but support is being a bit lacking. I know there's holidays and such but it's been a few months already with this issue, and this whole revert/install packages/reinstall/downgrade/etc. mess isn't helping much either.

Edit:

sudo dnf install https://github.com/filfreire/insomnia/releases/download/fedora-experiment%408ae4fe71/Insomnia.Core-2022.7.0-beta.5-fedora.rpm

Fixed it for me. Maybe mixed with @padys's workaround. I'm back again. What a mess :(

leonardehrenfried · 2022-12-23T16:49:10Z

Btw, i use the experimental build from here: #5281 (comment)

It's working fine for me on fedora 37.

sean-m-sullivan · 2022-12-28T14:19:58Z

I also used the experimental build, and my problems went away.

octaviobarbosa · 2023-01-09T20:38:22Z

Latest version 2022.7.1 still not working on fedora 37

tleepa · 2023-01-16T08:07:08Z

2022.7.2 is not working (showing the same SSL errors) even after compiling it myself, using #5088 (comment) workaround.

Edit: 2022.7.4 after re-compilation is not working either.

octaviobarbosa · 2023-01-17T18:30:59Z

2022.7.4 is not working yet... pls help us

octaviobarbosa · 2023-01-19T21:40:07Z

2022.7.5 is not working yet... on fedora 37

filfreire · 2023-01-20T17:06:00Z

Hi folks, I pushed a new experimental build from latest develop branch.

To install you can do:

sudo dnf install https://github.com/filfreire/insomnia/releases/download/fedora-experiment%407417acb/Insomnia.Core-2022.7.5-fedora.rpm

And if it still doesn't work, try the workaround mentioned here.

Also a small update. We're still looking into a proper fix for .rpm builds. We've recently managed to fix snapcraft builds so you may want to switch over to those while .rpm ones are not properly working. Sharing bellow some of the more recent findings:

Electron docs mentions that for fedora it needs the cups-devel dependency (example)
BUT, the underlying app-builder binary that electron-builder uses - is not adding that dependency in when running rpmbuild under the hood. This is what we use to build the current Insomnia .rpm package.

The hypothesis is - the docker build alternative pr that is used to create the experimental builds seems to solve it - because we add that cups dependency in and rebuild it in fedora environment from sources.

The definitive fix might be just making sure the cups related dependency is defined app-builder/electron-builder when it's running rpmbuild under the hood.

We're still looking into how to fix this properly, but in the meantime I would suggest you to either hold with the experimental builds or to try and use the snapcraft version instead.

If anyone from the community has a bit more in-deep knowledge and experience with building Electron for Fedora and have other hypothesis and suggestions please reach out.

Thanks folks 🙇

ontanj · 2023-01-23T13:11:33Z

The experimental builds does not work for me and I'm not interested in installing Snap.
I've just installed Postman. Hopefully this can be fixed before I get used to Postman.

filfreire · 2023-01-23T19:21:55Z

Quick follow-up update:
So it seems the only thing that consistently does the trick is the fix suggested by @padys in this comment. The experimental builds are not guaranteed to work.

Possible workaround

# remove existing insomnia installations
sudo dnf remove insomnia

# install latest insomnia
sudo dnf install https://github.com/Kong/insomnia/releases/download/core%402022.7.5/Insomnia.Core-2022.7.5.rpm

# download cups 2.4.1 libs and copy them to insomnia
curl -O https://kojipkgs.fedoraproject.org//packages/cups/2.4.1/7.fc36/x86_64/cups-libs-2.4.1-7.fc36.x86_64.rpm
rpm2cpio cups-libs-2.4.1-7.fc36.x86_64.rpm | cpio -idmv
sudo cp ./usr/lib64/libcups* /opt/Insomnia/.

# run insomnia
insomnia

Combinations tried:

appimage + system-level cups 2.4.2 🔴
rpm via built docker build + system-level cups 2.4.2 🔴
rpm built via docker build + system-level cups 2.4.1 ✅
rpm built via docker build + system-level cups 2.4.2 && copying cups 2.4.1 .so files into /opt/Insomnia ✅
2022.7.5 official .rpm && copying cups 2.4.1 .so files into /opt/Insomnia ✅
flatpak 2022.7.3 that uses cups 2.3.3 (see comment) ✅

The hypothesis I mentioned above, of cups not being strictly defined on electron-builder/app-builder now seems less likely. It might really be something to do with Fedora updating cups to 2.4.2.

This could also explain why regardless of using rpm or AppImage - any old or recent insomnia version would stop working the moment the system-level version of cups became 2.4.2.

Other notes:

https://bbs.archlinux.org/viewtopic.php?id=276719 - similar issue with 2.4.2 on Arch
An OpenSSL related fix added for future cups 2.4.3 OpenPrinting/cups@c0c4037 / IPP crashes after every successfully completed job since 2.4.2 OpenPrinting/cups#409

We'll update you folks as soon as we know more, but in the meantime please let us know if the workaround on this comment based on @padys original one also worked for you.

tleepa · 2023-01-24T06:10:30Z

Just to add to your combinations list:
The flatpak version (currently at 2022.7.3), which seems to be an rebuilt AppImage, is also working fine on my Fedora 37, without tinkering with cups package.

filfreire · 2023-01-24T09:05:56Z

@tleepa thanks. It looks like the flatpak base runtime used, 21.08, uses an older cups, version 2.3.3.

I suspect that if this PR gets merged, and the newer runtime includes cups 2.4.2, Insomnia https requests would also start failing for flatpak users.

azzamsa · 2023-03-13T08:07:12Z

@tleepa I suspect the flatpak version runs without any cups issue. However the last version is very outdated compared to upstream version.

Any update about this issue?

marcelsby · 2023-03-23T18:05:03Z

It worked for me!

Waiting for a definitive solution, thank you all! 🥳 🎉

stephan-uhlmann · 2023-05-10T19:10:03Z

Also openSUSE Tumbleweed is affected. It ships with libcups2-2.4.2-4.2.x86_64 and current Insomnia 2023.2.0 breaks/crashes as described. ;(
Unfortunately there is no 2.4.1 version of the rpm available anymore, so I couldn't test the described workaround.

padys · 2023-05-10T20:11:46Z

@stephan-uhlmann Maybe try any older version of libcups, even from RPM for previous version of openSuse.

stephan-uhlmann · 2023-05-11T14:19:05Z

I tried the libcups2-2.2.7-3.26.1.x86_64.rpm from openSUSE Leap 15.4 and even though via ld I could confirm that it was then loading that libcups.so.2 from inside the Insomnia installation directory instead of the system-installed, it was still crashing.
I then took the libcups.so.2 from cups-libs-2.4.1-7.fc36.x86_64.rpm from Fedora which was mentioned above, and with that it's not crashing. I didn't copy libcupsimage.so.2 so that seems to does not matter in this issue.
Really strange issue. I hope one day Insomnia devs can find an actual solution to it. Let me know if I can be of any help with testing.

darkguy2008 · 2023-06-02T09:12:12Z

I'm still getting this in Fedora 38, fresh install. Any known workarounds?

ivmilicevic · 2023-06-11T15:43:23Z

Workaround from comment #5088 (comment) works fine on Fedora 38.
I've installed Insomnia.Core-2023.2.2.rpm and copied libcups files per linked comment:

curl -O https://kojipkgs.fedoraproject.org//packages/cups/2.4.1/7.fc36/x86_64/cups-libs-2.4.1-7.fc36.x86_64.rpm
rpm2cpio cups-libs-2.4.1-7.fc36.x86_64.rpm | cpio -idmv
sudo cp ./usr/lib64/libcups* /opt/Insomnia/.

darkguy2008 · 2023-06-30T05:41:28Z

BTW I just tried 2023.3.0 and same thing. Is there any ETA on resolution instead of trying workarounds like the above?

vicenterusso · 2023-07-21T01:20:37Z

Hm, Fedora 38 with 2023.4.0, no errors. Can someone confirm please? Tried production https and local certificates too.

Installed RPM version

trunglebka · 2023-07-25T06:22:10Z

@vicenterusso
Mine worked too (Fedora 38 with 2023.4.0)

dhmw · 2023-08-22T16:17:53Z

2023.5.5 on fedora 38 works perfectly here.

Seil0 · 2023-08-23T15:14:48Z

2023.5.6 also works on openSUSE Tumbleweed with system level cups 2.4.2

trunglebka added B-bug Bug: general classification S-unverified Status: Unverified by maintainer labels Aug 17, 2022

filfreire added the O-linux Operating System: Linux label Aug 17, 2022

filfreire self-assigned this Aug 17, 2022

filfreire removed the S-unverified Status: Unverified by maintainer label Sep 6, 2022

filfreire mentioned this issue Dec 17, 2022

2022.7.0 snap wont start on ubuntu #5531

Closed

1 task

filfreire added N-help Needs: Help E-hard Experience required: Expert Level labels Jan 25, 2023

Nopraz mentioned this issue Jun 15, 2023

Bug close when press Send on OpenSUSE #6019

Open

1 task

Kong deleted a comment from vicenterusso Oct 25, 2023

Crash on Fedora 36 after got "Error: SSL connect error" when working with https websites #5088

Crash on Fedora 36 after got "Error: SSL connect error" when working with https websites #5088

Comments

trunglebka commented Aug 17, 2022 • edited by filfreire Loading

SEE UPDATE 23 January 2023

Workaround

Expected Behavior

Actual Behavior

Reproduction Steps

Is there an existing issue for this?

Additional Information

Insomnia Version

What operating system are you using?

Operating System Version

Installation method

Last Known Working Insomnia version

wongstein commented Aug 17, 2022

trunglebka commented Aug 17, 2022 • edited Loading

Rayvion commented Aug 18, 2022

davelima commented Aug 18, 2022

vavsab commented Aug 19, 2022

neo-donnie-walsh commented Aug 19, 2022

davelima commented Aug 23, 2022 • edited Loading

sarim commented Aug 23, 2022

zLupa commented Aug 24, 2022 • edited Loading

Nopraz commented Aug 24, 2022

octaviobarbosa commented Aug 25, 2022

AlenBenkovic commented Aug 26, 2022

filfreire commented Aug 26, 2022 • edited Loading

davelima commented Aug 26, 2022 • edited Loading

bisby commented Aug 26, 2022 • edited Loading

neo-donnie-walsh commented Aug 26, 2022

octaviobarbosa commented Aug 26, 2022

fhdiaze commented Aug 26, 2022 • edited Loading

sarim commented Aug 26, 2022

Nopraz commented Aug 29, 2022

filfreire commented Aug 29, 2022

Solution

vicenterusso commented Aug 30, 2022

sarim commented Sep 2, 2022 • edited Loading

darkguy2008 commented Sep 5, 2022

sarim commented Sep 5, 2022

ckujau commented Dec 9, 2022 • edited Loading

darkguy2008 commented Dec 23, 2022 • edited Loading

leonardehrenfried commented Dec 23, 2022

sean-m-sullivan commented Dec 28, 2022

octaviobarbosa commented Jan 9, 2023

tleepa commented Jan 16, 2023 • edited Loading

octaviobarbosa commented Jan 17, 2023

octaviobarbosa commented Jan 19, 2023

filfreire commented Jan 20, 2023 • edited Loading

ontanj commented Jan 23, 2023

filfreire commented Jan 23, 2023 • edited Loading

Possible workaround

tleepa commented Jan 24, 2023

filfreire commented Jan 24, 2023

azzamsa commented Mar 13, 2023 • edited Loading

marcelsby commented Mar 23, 2023

stephan-uhlmann commented May 10, 2023

padys commented May 10, 2023

stephan-uhlmann commented May 11, 2023

darkguy2008 commented Jun 2, 2023 • edited Loading

ivmilicevic commented Jun 11, 2023

darkguy2008 commented Jun 30, 2023

vicenterusso commented Jul 21, 2023

trunglebka commented Jul 25, 2023

dhmw commented Aug 22, 2023

Seil0 commented Aug 23, 2023

trunglebka commented Aug 17, 2022 •

edited by filfreire

Loading

trunglebka commented Aug 17, 2022 •

edited

Loading

davelima commented Aug 23, 2022 •

edited

Loading

zLupa commented Aug 24, 2022 •

edited

Loading

filfreire commented Aug 26, 2022 •

edited

Loading

davelima commented Aug 26, 2022 •

edited

Loading

bisby commented Aug 26, 2022 •

edited

Loading

fhdiaze commented Aug 26, 2022 •

edited

Loading

sarim commented Sep 2, 2022 •

edited

Loading

ckujau commented Dec 9, 2022 •

edited

Loading

darkguy2008 commented Dec 23, 2022 •

edited

Loading

tleepa commented Jan 16, 2023 •

edited

Loading

filfreire commented Jan 20, 2023 •

edited

Loading

filfreire commented Jan 23, 2023 •

edited

Loading

azzamsa commented Mar 13, 2023 •

edited

Loading

darkguy2008 commented Jun 2, 2023 •

edited

Loading