Flatpak: OrcaSlicer fails to launch on Intel Iris graphics, likely a race condition (works under strace) #500

Open
opened 2026-04-05 16:21:47 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @BlackTeaLeaf on 3/3/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.2-rc

Operating System (OS)

Linux

OS Version

Nobara Linux 43

Additional system information

  • OS: Nobara Linux 43
  • Kernel: 6.18.7-200.nobara.fc43.x86_64
  • Desktop Environment: KDE Plasma 6.5.4 (Wayland)
  • Qt Version: 6.10.1
  • CPU: Intel® Core™ Ultra 5 125H (18 cores)
  • GPU: Intel® Arc Graphics
  • Memory: 16 GiB
  • Hardware: Acer Swift SFG14-73

Printer

Bambulab H2D

How to reproduce

  1. Install io.github.softfever.OrcaSlicer using the Flatpak file downloaded from GitHub Releases on the hardware specified above (fast CPU + Intel Arc Graphics).
  2. Launch the application normally via the application menu or terminal: flatpak run io.github.softfever.OrcaSlicer.

Actual results

The application process starts and displays the splash screen briefly, but then exits silently within a few seconds before the main window appears. No error message is printed in the standard output.

Expected results

The OrcaSlicer main window should appear and the application should be usable without needing to be attached to strace or gdb.

Project file & Debug log uploads

report.zip

Checklist of files to include

  • Log file
  • Project file

Anything else?

Note: English is not my native language. I have limited experience with C++ development, and the detailed analysis below was conducted with the assistance of AI tools to interpret the debugging logs and identify the race condition.

The Flatpak version of OrcaSlicer (io.github.softfever.OrcaSlicer) fails to launch on my system. The splash screen (logo and version) appears briefly, but the process exits silently before the main window appears, without any error message being printed.

The AppImage version of OrcaSlicer and the Flatpak version of BambuStudio both work correctly on the same system. However, I would prefer to use the Flatpak version to enable automatic updates for OrcaSlicer.

Diagnostic Analysis & Key Findings

This appears to be a race condition during application initialization. The bug disappears when the application's execution is slowed down by a debugger or tracing tool.

  1. FAILS under normal execution. The process exits immediately.
  2. WORKS when launched under gdb (likely due to the delay introduced by loading debug symbols).
  3. WORKS when launched under strace. The overhead of intercepting system calls slows down the execution enough to bypass the race condition.
    • Command used: flatpak run --devel --command=strace io.github.softfever.OrcaSlicer -f /app/bin/orca-slicer 2>/dev/null

Current Workaround

I am currently using a wrapper script to launch the app via strace as a permanent workaround.

*Originally created by @BlackTeaLeaf on 3/3/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-rc ### Operating System (OS) Linux ### OS Version Nobara Linux 43 ### Additional system information * **OS:** Nobara Linux 43 * **Kernel:** 6.18.7-200.nobara.fc43.x86_64 * **Desktop Environment:** KDE Plasma 6.5.4 (Wayland) * **Qt Version:** 6.10.1 * **CPU:** Intel® Core™ Ultra 5 125H (18 cores) * **GPU:** Intel® Arc Graphics * **Memory:** 16 GiB * **Hardware:** Acer Swift SFG14-73 ### Printer Bambulab H2D ### How to reproduce 1. Install io.github.softfever.OrcaSlicer using the Flatpak file downloaded from GitHub Releases on the hardware specified above (fast CPU + Intel Arc Graphics). 2. Launch the application normally via the application menu or terminal: `flatpak run io.github.softfever.OrcaSlicer`. ### Actual results The application process starts and displays the splash screen briefly, but then exits silently within a few seconds before the main window appears. No error message is printed in the standard output. ### Expected results The OrcaSlicer main window should appear and the application should be usable without needing to be attached to `strace` or `gdb`. ### Project file & Debug log uploads [report.zip](https://github.com/user-attachments/files/25708999/report.zip) ### Checklist of files to include - [x] Log file - [ ] Project file ### Anything else? **Note:** English is not my native language. I have limited experience with C++ development, and the detailed analysis below was conducted with the assistance of AI tools to interpret the debugging logs and identify the race condition. The Flatpak version of OrcaSlicer (io.github.softfever.OrcaSlicer) fails to launch on my system. The splash screen (logo and version) appears briefly, but the process exits silently before the main window appears, without any error message being printed. The AppImage version of OrcaSlicer and the Flatpak version of BambuStudio both work correctly on the same system. However, I would prefer to use the Flatpak version to enable automatic updates for OrcaSlicer. ### Diagnostic Analysis & Key Findings This appears to be a **race condition** during application initialization. The bug disappears when the application's execution is slowed down by a debugger or tracing tool. 1. **FAILS** under normal execution. The process exits immediately. 2. **WORKS** when launched under `gdb` (likely due to the delay introduced by loading debug symbols). 3. **WORKS** when launched under `strace`. The overhead of intercepting system calls slows down the execution enough to bypass the race condition. * Command used: `flatpak run --devel --command=strace io.github.softfever.OrcaSlicer -f /app/bin/orca-slicer 2>/dev/null` ### Current Workaround I am currently using a wrapper script to launch the app via `strace` as a permanent workaround.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#500