Can't run on Arch Linux recently

Hello, I’ve been using Logic 2 perfectly fine on Arch Linux (using the AUR package AUR (en) - saleae-logic2) for a while now. But since yesterday, I only seem to get a blank screen.

Here’s my logs:

Environment
  Executable path: /opt/saleae-logic2/Logic
  Executable directory: /opt/saleae-logic2
  Original working directory: /home/peter
  Current working directory: /opt/saleae-logic2
  Process ID: 14528
Crash reporting enabled. Machine ID: 21856861-057c-4df4-a7bc-4398c5722b6c
[14578:0828/135432.384252:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[14578:0828/135500.205237:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[14578:0828/135502.218177:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
^C⏎                                                                                                                          

I have added an AppArmour profile and loaded it just in the case that is the issue:

abi <abi/4.0>,
include <tunables/global>

profile Logic /opt/saleae-logic2/Logic flags=(unconfined) {
  userns,
  include if exists <local/Logic>
}

Here’s a screenshot of all I see:

I’ve also tried running with –no-gpu and –no-sandbox or with –enable-features=UseOzonePlatform –ozone-platform=wayland which all don’t seem to help (though those last flags seem to suppress the VSync error?). I have reinstalled, rebooted, etc.

Any ideas?

Small update, I am able to run through an ubuntu distrobox, but this isn’t an ideal solution.

Sorry for the trouble! We have not seen this before, unfortunately.

Can you try two more things:

  1. Set the environment variable ELECTRON_ENABLE_LOGGING=1 and if you get any additional logging output, send it our way.

  2. Add the --in-process-gpu flag

Also, do you know if any other electron applications are working on your system? common examples are Slack, Discord, Notion’s desktop app, the Figma desktop app, and VS Code. Electron also has a demo app / API explorer that you can get binaries for here: Releases · electron/electron-api-demos · GitHub if you don’t have another electron application already installed to test.

Also, when you say “A blank screen” do you mean a window actually opens? Does it stay open, or close on its own? From your screenshot it’s not clear what I’m seeing other than a terminal - is the bottom part our application, perhaps running in a tiling window manager?

Here’s the updated logs with those flags, it took a while for the vulkan errors to pop up. I don’t have a GPU other than the integrated intel iRIS Xe graphics:

Environment
  Executable path: /opt/saleae-logic2/Logic
  Executable directory: /opt/saleae-logic2
  Original working directory: /home/peter
  Current working directory: /opt/saleae-logic2
  Process ID: 1194452
Crash reporting enabled. Machine ID: 21856861-057c-4df4-a7bc-4398c5722b6c
[1194452:0829/103140.401092:WARNING:electron_api_native_image.cc(194)] Failed to load image from path '/opt/saleae-logic2/resources/linux-x64/LogicIcon.png'
[1194452:0829/103140.589197:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[1194452:0829/103144.714593:INFO:CONSOLE(45)] "the shortcut %s has multiple commands (%O) registered that do not allow shortcut overlap CmdOrCtrl+a markers:all-selected,advancedMeasurements:select-all-ranges", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (45)
[1194452:0829/103144.870554:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

[1194452:0829/103341.996850:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[1194452:0829/103353.361448:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
@saleae/electron/main: windows closed {}

Applications like vscodium work fine.

Yeah that screenshot shows the terminal I launched Logic 2 from, and the blank gray window below is Logic 2. I’m using sway for a tiling wm.

Another small update, installing vulkan-intel seems to fix the Vulkan issue, and yet Logic still does not launch properly (still that blank screen).

Hi @petercsmith-x

Sorry for the delay. We don’t have a lead on this, but I did remember one more thing to do to potentially collect more data.

Can you run with the same environment variables as last time, but also add ENABLE_DEVTOOLS=1

Given that a window opened at all, that indicates that the electron main process was able to launch an electron browser window. The flag above should trigger the chrome dev tools to open at the same time. If they do, please navigate to the console tab and send us any output you find there.

Also, I noticed in your initial message, you tested with -no-gpu and -no-sandbox

Those might not have been correct.

Can you try with --disable-gpu and --no-sandbox?

It seems very likely that you already tested no-sandbox with double leading dashes, but our forum editor merged them into one longer dash, but I just wanted to check.

I don’t know if --no-gpu is a recognized flag, but we’re only aware of --disable-gpu, so there is a chance that might fix it, or at least provide us more information.

Both the elements view and console view are blank when running with ENABLE_DEVTOOLS=1. I was using --no-sandbox with two hyphens, but for some reason the forum editor decided to create an en-dash from them. --disable-gpu didn’t help either. Same sort of logs as before, though I did notice something interesting with the infamous [object Object]:

Environment
  Executable path: /opt/saleae-logic2/Logic
  Executable directory: /opt/saleae-logic2
  Original working directory: /home/peter
  Current working directory: /opt/saleae-logic2
  Process ID: 1408587
Crash reporting enabled. Machine ID: 21856861-057c-4df4-a7bc-4398c5722b6c
[1408587:0904/100010.161771:WARNING:electron_api_native_image.cc(194)] Failed to load image from path '/opt/saleae-logic2/resources/linux-x64/LogicIcon.png'
[1408587:0904/100010.207850:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[1408620:0904/100010.221333:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[1408587:0904/100010.498986:INFO:CONSOLE(593)] "@saleae/logic/startup: renderer process started [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (593)
[1408587:0904/100010.704687:INFO:CONSOLE(45)] "the shortcut %s has multiple commands (%O) registered that do not allow shortcut overlap CmdOrCtrl+a markers:all-selected,advancedMeasurements:select-all-ranges", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (45)

This was run with:

ELECTRON_ENABLE_LOGGING=1 ENABLE_DEVTOOLS=1 saleae-logic2 --disable-gpu --no-sandbox

Oh, suddenly everything is seemingly working, had to wait a while (~36 seconds looking at the logs).

Here’s the logs (too long for forum so in a pastebin): https://privatebin.net/?b6cb597d48cfca46#8WGJACGYyvATg1mUBHpU8NdzA3yXdTXTchWnpnJXF8kw

I ran logic again and had the same issue and it took longer to start but at least it starts now.

Hi @petercsmith-x,

Thanks for the logs, and I’m glad to hear that is actually does run, despite the extremely long launch time.

This is the spot in the logs where the delay happens, right?

[1408587:0904/100010.704687:INFO:CONSOLE(45)] "the shortcut %s has multiple commands (%O) registered that do not allow shortcut overlap CmdOrCtrl+a markers:all-selected,advancedMeasurements:select-all-ranges", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (45)
[1408587:0904/100146.672669:INFO:CONSOLE(834)] "console.group", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (834)

The first log message (the shortcut…) that’s normal (something we want to fix, but it’s a low priority) and that indicates that our front end application code has started running normally.

The following line, after the long delay (console.group, and the subsequent response came back, but…) that message, which doesn’t always appear, indicates one of the first messages back from our native module, and this particular message appears after we finish checking for installed analyzer plugins on the system.

This could indicate a few problems:

  1. There could be a general problem loading our native back-end shared library. This is opened with dlopen. It would not shock me if something might cause that to get delayed, but I’m not sure what.
  2. There could be an issue searching for protocol analyzers. Any chance you set the “Custom Low Level Analyzers” directory in the settings? Perhaps to a directory that contained many, many shared libraries? Or perhaps set it to a network directory, or an unusual disk, or some other location that would have a long pause on first access?

Also, have you noticed any operations taking a long time in the application? For example, if you open the application, then connect one of our devices, does it take a long time to get detected? What about saving or exporting a file? Any chance that hangs up for a while at the start?

These are rough guesses as to the problem. Unfortunately it’s still pretty hard to tell what’s happening.

I have been struggling with the same issue, although using an AMD iGPU (6800U). Also observed on an AMD 7840U.

  • Logic 2 had launched normally on both systems months ago, but it’s unknown whether it was an upgrade of Logic 2 or a system package that resulted in the regression.
  • Logic 2 is the only Electron app that is having any observable issues.
  • Logic 2 window opens immediately but remains blank for about 2 minutes and 30 seconds. Once the window is populated with all of the GUI elements, the Logic Pro 16 connects immediately and everything works as one would expect.
  • Custom Low Level Analyzers path is unset.
$ ELECTRON_ENABLE_LOGGING=1 ENABLE_DEVTOOLS=1 saleae-logic2 --disable-gpu --no-sandbox
Environment
  Executable path: /opt/saleae-logic2/Logic
  Executable directory: /opt/saleae-logic2
  Original working directory: /home/REDACTED
  Current working directory: /opt/saleae-logic2
  Process ID: 4256
Crash reporting enabled. Machine ID: REDACTED
[4256:0905/075641.994392:WARNING:electron_api_native_image.cc(194)] Failed to load image from path '/opt/saleae-logic2/resources/linux-x64/LogicIcon.png'
[4256:0905/075642.044273:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[4286:0905/075642.116814:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[4256:0905/075642.797228:INFO:CONSOLE(593)] "@saleae/logic/startup: renderer process started [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (593)
[4256:0905/075643.347859:INFO:CONSOLE(45)] "the shortcut %s has multiple commands (%O) registered that do not allow shortcut overlap CmdOrCtrl+a markers:all-selected,advancedMeasurements:select-all-ranges", source: file:///opt/saleae-log
[4256:0905/075917.948241:INFO:CONSOLE(834)] "console.group", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (834)
[4256:0905/075917.948980:INFO:CONSOLE(2275)] "response came back, but no matching callback or pipe subscriber was found. Id: 0", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075917.949035:INFO:CONSOLE(2275)] "type: response", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075917.949111:INFO:CONSOLE(2275)] "[object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075917.949409:INFO:CONSOLE(834)] "console.groupEnd", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (834)
[4256:0905/075918.178026:INFO:CONSOLE(2275)] "@saleae/logic/graph: create node [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075918.184245:INFO:CONSOLE(2275)] "@saleae/logic/automation: Configuring automation server [object Object] [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075918.187121:INFO:CONSOLE(2275)] "@saleae/logic/automation: Shutdown finished [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075920.651838:INFO:CONSOLE(2275)] "@saleae/logic/devices: Got deviceconfig [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075920.658669:INFO:CONSOLE(2275)] "@saleae/logic/session: Session construction started. [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075920.692212:INFO:CONSOLE(2275)] "@saleae/logic/devices: Preparing to acquire device REDACTED for session 0
    at F.prepareToAcquireDevice (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:39644)
    at L.acquireDevice (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:84:25213)
    at J.createSession (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:229:168846)
    at async t (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:43091)
    at async F.handleNewDevices (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:46494) [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075920.694373:INFO:CONSOLE(2275)] "@saleae/logic/graph: create node [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
...repeats 174 times...
[4256:0905/075920.729993:INFO:CONSOLE(2275)] "@saleae/logic/devices: Acquired device REDACTED for session 0 [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075920.881941:INFO:CONSOLE(2275)] "invoking a computedFn from outside an reactive context won't be memoized, unless keepAlive is set", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.306547:INFO:CONSOLE(2275)] "@saleae/logic/graph: node action [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
...repeats 32 times...
[4256:0905/075921.344385:INFO:CONSOLE(2275)] "@saleae/logic/graph: create node [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.346025:INFO:CONSOLE(2275)] "@saleae/logic/graph: create node [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.348556:INFO:CONSOLE(2275)] "@saleae/logic/graph: send to pipe [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.351230:INFO:CONSOLE(2275)] "@saleae/logic/graph: send to pipe [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.370926:INFO:CONSOLE(2275)] "@saleae/logic/session: selecting session [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/075921.371427:INFO:CONSOLE(2275)] "@saleae/logic/devices: Preparing to acquire device REDACTED for session 0
    at F.prepareToAcquireDevice (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:39644)
    at L.acquireDevice (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:84:25213)
    at $.select (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:83639)
    at async J.createSession (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:229:170482)
    at async t (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:43091)
    at async F.handleNewDevices (file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js:1397:46494) [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4286:0905/075921.554926:ERROR:gl_utils.cc(402)] [.WebGL-0x55a5fb4ac800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[4256:0905/075921.583956:INFO:CONSOLE(0)] "[.WebGL-0x55a5fb4ac800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/index.html?log_file_name=%2Fhome%2FREDACTED%2F.config%2FLogic%2Flogs%2F2025-09-05_07-56-42_ce9d412f-e57e-48d9-81d8-03eff2d85f21%2Fgraphio.log&launchId=ce9d412f-e57e-48d9-81d8-03eff2d85f21&logic_shared_path=%2Fopt%2Fsaleae-logic2%2Fresources%2Flinux-x64%2Flibgraph_server_shared.so&python_home_path=%2Fopt%2Fsaleae-logic2%2Fresources%2Flinux-x64%2Fpythonlibs&automation=off&automation_port=10430&automation_host=127.0.0.1 (0)
[4286:0905/075921.606915:ERROR:gl_utils.cc(402)] [.WebGL-0x55a5fb4ac800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[4256:0905/075921.622570:INFO:CONSOLE(0)] "[.WebGL-0x55a5fb4ac800]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/index.html?log_file_name=%2Fhome%2FREDACTED%2F.config%2FLogic%2Flogs%2F2025-09-05_07-56-42_ce9d412f-e57e-48d9-81d8-03eff2d85f21%2Fgraphio.log&launchId=ce9d412f-e57e-48d9-81d8-03eff2d85f21&logic_shared_path=%2Fopt%2Fsaleae-logic2%2Fresources%2Flinux-x64%2Flibgraph_server_shared.so&python_home_path=%2Fopt%2Fsaleae-logic2%2Fresources%2Flinux-x64%2Fpythonlibs&automation=off&automation_port=10430&automation_host=127.0.0.1 (0)
[4256:0905/080002.683755:ERROR:CONSOLE(1)] "Uncaught (in promise) TypeError: Failed to fetch", source: devtools://devtools/bundled/panels/elements/elements.js (1)
[4256:0905/080004.533570:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: closeCallback [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.535076:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: beforeUnloadCallback [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.535658:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: Unload not started - starting cleanup [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.552242:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: Preventing close [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.552781:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: Unload complete [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.553078:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: Destroying window [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.557918:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: closeCallback [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
[4256:0905/080004.558292:INFO:CONSOLE(2275)] "@saleae/logic/run-on-close: beforeUnloadCallback [object Object]", source: file:///opt/saleae-logic2/resources/app.asar/dist/logic/bundle.js (2275)
@saleae/electron/main: windows closed {}
[4286:0905/080004.578071:WARNING:connection.cc(41)] X error received.  Request: Shm::PutImageRequest, Error: DrawableError{.sequence = 1131, .bad_value = 4194307, .minor_opcode = 3, .major_opcode = 130}

Maybe its helpful to let you know that I have just had a very similar experience on Fedora 42.

Its a new PC with a fresh install of fedora so no existing settings. libnsl and libxcrypt-compat are installed

I have been only seeing:

tom@triadeca:~/opt/salea$ ./Logic-2.4.29-linux-x64.AppImage --no-sandbox --disable-gpu
/tmp/.mount_Logic-OCknUX ~/opt/salea
~/opt/salea
Environment
Executable path: /tmp/.mount_Logic-OCknUX/Logic
Executable directory: /tmp/.mount_Logic-OCknUX
Original working directory: /home/tom/opt/salea
Current working directory: /tmp/.mount_Logic-OCknUX
Process ID: 16883
Crash reporting enabled. Machine ID: <>
^C^C

The behaviour and output was the same without the args. I did not see a gui at all.

I also tried an older version I had on another machine:

tom@triadeca:~/opt/salea$ ./Logic-2.4.14-linux-x64.AppImage
/tmp/.mount_Logic-kAzGVm ~/opt/salea
~/opt/salea
Environment
Executable path: /tmp/.mount_Logic-kAzGVm/Logic
Executable directory: /tmp/.mount_Logic-kAzGVm
Original working directory: /home/tom/opt/salea
Current working directory: /tmp/.mount_Logic-kAzGVm
Process ID: 8059
Crash reporting enabled. Machine ID: <>
[8142:0905/131845.544462:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[8142:0905/131845.576252:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[8142:0905/131845.593153:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
error submitting otlp telemetry request: FetchError: request to https://o11y.saleae.com/v1/logs failed, reason: getaddrinfo ENOTFOUND o11y.saleae.com
at ClientRequest. (/tmp/.mount_Logic-kAzGVm/resources/app.asar/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:514:28)
at TLSSocket.socketErrorListener (node:_http_client:501:9)
at TLSSocket.emit (node:events:514:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: ‘system’,
errno: ‘ENOTFOUND’,
code: ‘ENOTFOUND’
}
error submitting otlp telemetry request: FetchError: request to https://o11y.saleae.com/v1/logs failed, reason: getaddrinfo ENOTFOUND o11y.saleae.com
at ClientRequest. (/tmp/.mount_Logic-kAzGVm/resources/app.asar/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:514:28)
at TLSSocket.socketErrorListener (node:_http_client:501:9)
at TLSSocket.emit (node:events:514:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: ‘system’,
errno: ‘ENOTFOUND’,
code: ‘ENOTFOUND’
}

With noted Irony, it started after a longer wait while reading this forum post.

Maybe that helps somehow.

Thanks

Hello, I have exactly the same problem. While waiting for the window to appear, I noticed that a core dump is always created. With my 32GB RAM, this takes a while. I then disabled the creation of core dumps. After that, the window appears immediately at startup. This is a workaround; the actual error causing something to crash in the background should be fixed.

Oh boy, judging by all the new folks here, it sounds like this may end up affecting quite a few users.

@awahab - could you let me know what distro you are using, and send the output of uname -a?

@shortst - could you let me know what graphics card/adapter your computer is using?

@stone - could you send me your distro name & version, the output of uname -a, and what graphics card/adapter you are using?

In the meantime, I’ll see if I can reproduce this over here.

My guess is that our software is not playing well with some sort of recent package update.

Hello all,

I’ve recently tried and failed to reproduce this on a completely up to date Fedora 42 install.

stone mentioned that a core dump was being generated. We would greatly appreciate copies of crash files from anyone who is getting them. @stone I’ve recently emailed you a Dropbox upload link which you can use to send us the core file.

If anyone else has a core file they can send, please let us know! If it’s small enough to attach to an email, please send it to us here: https://contact.saleae.com/hc/en-us/requests/new otherwise let me know (either here or via our support contact form) and I can send you an upload URL.

Also, please send us your machine IDs - these are UUIDs generated at random the first time you open the app, which we attach to crash reports that are automatically uploaded when crash reporting is enabled. It’s shown at the start of the console output. This will allow us to check for crash reports automatically uploaded from your machine, if there are any. Feel free to post here or send it in via a support ticket, using the same contact link above.

Again, I apologize for the trouble with this, and look forward to getting it solved soon. Thanks for all the details provided so far!

-Mark

@markgarrison, thanks for being so responsive!

Linux 6.16.4-arch1-1 #1 SMP PREEMPT_DYNAMIC x86_64 GNU/Linux

Thanks, I appreciate the prompt attention

Hardware context: It is the graphics in the Intel(R) Core™ Ultra 7 265U. In a laptop, through a thunderbolt4 dock to multiple monitors.

EDIT: I see the same behaviour without dock/external monitors

tom@triadeca:~$ sudo lshw -C display
*-display
description: VGA compatible controller
product: Arrow Lake-U [Intel Graphics]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: iomemory:400-3ff iomemory:400-3ff irq:194 memory:4058000000-4058ffffff memory:4000000000-400fffffff memory:c0000-dffff memory:405c000000-4062ffffff


Here is the full terminal log:

tom@triadeca:~/opt/salea$ ./Logic-2.4.29-linux-x64.AppImage
/tmp/.mount_Logic-oZMBAk ~/opt/salea
~/opt/salea
Environment
Executable path: /tmp/.mount_Logic-oZMBAk/Logic
Executable directory: /tmp/.mount_Logic-oZMBAk
Original working directory: /home/tom/opt/salea
Current working directory: /tmp/.mount_Logic-oZMBAk
Process ID: 195728
Crash reporting enabled. Machine ID: 29e189a3-48b3-45aa-940a-691eb0281609
[195823:0907/112442.261542:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[195823:0907/112442.264315:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[195823:0907/112444.528396:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
@saleae/electron/main: windows closed {}

The delay is between Crash reporting… and [195823:0…


The coredump is 45MB compressed but it seems I cant upload it here.

Don’t hesitate to ask if there is anything else I can send.

Thanks,

Tom

Hi, my system is a Arch Linux on AMD Ryzen 7 4800H with integrated Radeon Graphics.
The kernel is:

6.16.0-arch2-1 #1 SMP PREEMPT_DYNAMIC Wed, 13 Aug 2025 23:38:48 +0000 x86_64 GNU/Linux

Desktop is Gnome 48 on Wayland

There could be an issue searching for protocol analyzers. Any chance you set the “Custom Low Level Analyzers” directory in the settings? Perhaps to a directory that contained many, many shared libraries? Or perhaps set it to a network directory, or an unusual disk, or some other location that would have a long pause on first access?

I don’t have the “Custom Low Level Analyzers” option set so it isn’t that at least.

Also, have you noticed any operations taking a long time in the application? For example, if you open the application, then connect one of our devices, does it take a long time to get detected? What about saving or exporting a file? Any chance that hangs up for a while at the start?

Nope, seems to work perfectly fine once it is running.

I ran strace on it, and its hard to tell because the logs move fast, but if it helps, when it starts working it pretty immediately tries to openat some $HOME/.config/user-dirs.dirs (which doesn’t exist on my machine).

There is a lot of repeated output in the strace while logic is blank that looks a bit like:

ppoll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}], 4, {tv_sec=36, tv_nsec=213000000}, NULL, 8) = 1 ([{fd=13, revents=POLLIN}], left {tv_sec=34, tv_nsec=280421622})
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
read(13, "!", 2)                        = 1
write(31, "\1\0\0\0\0\0\0\0", 8)        = 8
openat(AT_FDCWD, "/home/peter/.config/Logic/config.json", O_RDONLY|O_CLOEXEC) = 100
statx(100, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=26057, ...}) = 0
read(100, "{\n\t\"appIdentification\": {\n\t\t\"mac"..., 26057) = 26057
close(100)                              = 0
epoll_wait(26, [{events=EPOLLIN, data=0x1f}], 1024, 0) = 1
read(31, "\1\0\0\0\0\0\0\0", 1024)      = 8
futex(0x56102bf95088, FUTEX_WAKE_PRIVATE, 1) = 1
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(48, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}], 4, {tv_sec=0, tv_nsec=0}, NULL, 8) = 0 (Timeout)
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(48, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}], 4, {tv_sec=34, tv_nsec=273000000}, NULL, 8) = 1 ([{fd=13, revents=POLLIN}], left {tv_sec=29, tv_nsec=277783620})
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
read(13, "!", 2)                        = 1
write(31, "\1\0\0\0\0\0\0\0", 8)        = 8
openat(AT_FDCWD, "/home/peter/.config/Logic/config.json", O_RDONLY|O_CLOEXEC) = 100
statx(100, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=26057, ...}) = 0
read(100, "{\n\t\"appIdentification\": {\n\t\t\"mac"..., 26057) = 26057
close(100)                              = 0
epoll_wait(26, [{events=EPOLLIN, data=0x1f}], 1024, 0) = 1
read(31, "\1\0\0\0\0\0\0\0", 1024)      = 8
futex(0x56102bf95088, FUTEX_WAKE_PRIVATE, 1) = 1
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(48, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}], 4, {tv_sec=0, tv_nsec=0}, NULL, 8) = 0 (Timeout)
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(48, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=47, events=POLLIN}, {fd=48, events=POLLIN}], 4, {tv_sec=29, tv_nsec=268000000}, NULL, 8) = 1 ([{fd=13, revents=POLLIN}], left {tv_sec=24, tv_nsec=273539915})
recvmsg(47, {msg_namelen=0}, 0)         = -1 EAGAIN (Resource temporarily unavailable)

But nothing really jumps out to me. There is a lot of recvmsg returning EAGAIN which continues once logic actually loads.

Thanks again everyone.

It turns out I can reproduce it locally now. After I updated my Fedora install, I did not log out or reboot. After logging out & logging back in, I’m able to reproduce the problem.

I’ll let you know as soon as I have an update.

Thanks!

-Mark