Crash on startup / openSUSE Tumbleweed

Hi,

I’m attempting to run Logic-2.3.39-master.AppImage. This is what happens (launching from terminal):

> ./Logic-2.3.39-master.AppImage 
/tmp/.mount_Logic-xCYegK ~/app
~/app
ATTENTION: Sandboxing of this app has been disabled since the user namespace feature of your OS is disabled.
Please enable user namespaces or use the deb package.
Environment
  Executable path: /tmp/.mount_Logic-xCYegK/Logic
  Executable directory: /tmp/.mount_Logic-xCYegK
  Original working directory: /home/paradajz/app
  Current working directory: /tmp/.mount_Logic-xCYegK
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
Attempting to call a function in a renderer window that has been closed or released.
Function provided here: bundle.js:2139:6398
Remote event names: close

The app opens for roughly 2 seconds and then it crashes immediately.

On a similar note, trying to launch last v1 version results in this:

> ./Logic 
Root Path: /home/paradajz/app/Logic+1.2.18+(64-bit)/Logic 1.2.18 (64-bit)  [ /home/build/ob_logic/Source/Environment.cpp; Environment; 158 ]
Writeable Root Path: /home/paradajz/app/Logic+1.2.18+(64-bit)/Logic 1.2.18 (64-bit)  [ /home/build/ob_logic/Source/Environment.cpp; Environment; 185 ]
Temp Folder path: /tmp  [ /home/build/ob_logic/Source/Environment.cpp; Environment; 191 ]
Release Mode; analyzer path is /home/paradajz/app/Logic+1.2.18+(64-bit)/Logic 1.2.18 (64-bit)/Analyzers  [ /home/build/ob_logic/Source/Environment.cpp; Environment; 201 ]
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
  [ /home/build/ob_logic/Source/UsbDevice.cpp; UsbDevice; 62 ]
  [ /home/build/ob_logic/Source/UsbDevice.cpp; IsFirmwareDownloaded; 142 ]
4 endpoints  [ /home/build/ob_logic/Source/UsbDevice.cpp; IsFirmwareDownloaded; 146 ]
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init
qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method
qt.network.ssl: QSslSocket: cannot call unresolved function sk_num
First device connected. Creating Primary Display.  [ /home/build/ob_logic/Source/LogicWindow_Devices.cpp; AttachedDevicesChangedSlot; 70 ]
GeneratePixmapEllipses: 0,864534 seconds  [ /home/build/ob_logic/Source/AnalogDisplayEngine.cpp; AnalogDisplayEngine; 38 ]
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
device change has triggered sprucing up the empty capture tab.  [ /home/build/ob_logic/Source/LogicWindow_Controller.cpp; ActiveDeviceChanged; 460 ]
setting PrimaryDisplay's Session to NULL.  [ /home/build/ob_logic/Source/PrimaryDisplay.cpp; SetSession; 562 ]
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Segmentation fault (core dumped)

@paradajz This is certainly strange behavior. Although our software doesn’t officially support openSUSE Tumbleweed, I have some follow questions for you below to potentially help us get to the bottom of this.

  1. How does Logic v1 behave? Does it eventually crash like Logic v2? If so, can you try the solution highlighted in the support article below?
    Linux Permission Requirements for Logic Software - Saleae Support

  2. As for running the Logic v2 software in openSUSE, I suspect that insufficient permissions may not be an issue since the app does launch briefly. I’m not quite sure if this will help, but the Ubuntu instructions for launching the app directly from the AppImage file is below. Does openSUSE have a similar file property setting that you can try?
    Installation - Saleae Support

  3. Did you notice the same behavior in older Logic v2 versions? I’m wondering if this is specifically caused by the latest version. Please give v2.3.37 a try below. Versions v2.3.38 and onwards added several major updates so I’m wondering if anything from these versions broke it for you.
    Saleae

Thanks for the response.

Regarding v2, yes, the executable flag is set (otherwise I wouldn’t be able to open it at all). This is the first v2 version I have ever tried. Same thing happens on .37.
Regarding v1 - that one doesn’t open at all - I just get the segfault in terminal and that’s all. However - it used to work just fine. I guess some update on my system broke it (I use rolling distro, after all).

EDIT: I realize I’m on unsupported distro so if this is something distro-specific I don’t mind - the software works fine on Windows, but I’d be happy to provide you with any info you might require.

1 Like

@paradajz,

I’m not sure why both applications are crashing on launch. Do you have one of our devices attached to your system? If so, please remove it, and try again.

Also, you might want to try exacting the AppImage and running the software directly. I’m not on a Linux machine at the moment, but I think this should do it:

./Logic-2.3.39-master.AppImage --appimage-extract
cd squash-fs
./Logic

Let me know if the console output is any different.

Second, this could be a problem with a dependency of our data processing back-end not found. This would not show up in ldd for either the AppImage or the extracted logic binary, because it’s loaded at runtime.

Instructions for checking for missing dependencies can be found here:

Specifically the part that asks you to run ldd & ldd -v.

Please send the output our way, and if you notice any missing dependencies, try installing them too.

Just on the off chance it’s the same issue - on Fedora it crashes on startup due to a libcrypto mismatch.

The following works for me;
LD_PRELOAD=/usr/lib64/libcrypto.so.1.1 ./Logic-2.3.39-master.AppImage