Flatpak version crashes on Device tab (Mainsail load) on Linux Mint with Intel Graphics #338

New Issue

MrUnknownDE · 2026-04-05T16:20:01+02:00

MrUnknownDE commented

2026-04-05 16:20:01 +02:00

Originally created by @SergeiVaidie on 3/12/2026

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.2-rc2 (Flatpak version from Flathub)

Operating System (OS)

Linux

OS Version

Linux Mint 22.3 "Zena" (based on Ubuntu 24.04)

Additional system information

CPU: 11th Gen Intel© Core™ i5-1135G7 @ 2.40GHz × 4
RAM: 32 GB
Graphics Hardware: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (integrated)
Graphics Drivers: Mesa 25.2.8-0ubuntu0.24.04.1 (confirmed via glxinfo)
Desktop Environment: Cinnamon 6.6.7 (X11 session)

Printer

Anycubic Kobra S1 Combo with Rinkhals

How to reproduce

Install the Flatpak version of OrcaSlicer on a compatible Linux system.
Configure a printer with a valid Moonraker connection (e.g., 192.168.1.51).
Open OrcaSlicer and click on the Device tab.
Observe the Mainsail interface starting to load in the panel, followed by the immediate and silent crash of the whole application.

Actual results

The OrcaSlicer Flatpak version (io.github.orcaslicer.OrcaSlicer) crashes consistently and silently when switching to the Device tab. The Mainsail web interface begins to load, and then the entire application closes without an error dialogue. The application runs fine on the Prepare and Preview tabs.

Expected results

The Device tab should load and display the Mainsail (or Fluidd) interface correctly, allowing for printer control and monitoring, just as it does in a regular web browser.

Project file & Debug log uploads

Debug log --> debug_Thu_Mar_12_23_36_06_2.log.0.zip

Checklist of files to include

Log file
Project file

Anything else?

I have conducted extensive troubleshooting with a user facing this exact issue and can confirm the following attempted fixes did not resolve the crash:

Ensuring the correct Moonraker port (:7125) is used in the printer host configuration.
Setting WEBKIT_DISABLE_DMABUF_RENDERER=1 environment variable.
Unsetting the DRI_PRIME environment variable in the Flatpak.
Forcing the Flatpak to use only the X11 socket (--socket=x11 --nosocket=wayland).
Forcing software rendering with LIBGL_ALWAYS_SOFTWARE=1.
Forcing an alternative WebKit backend with WEBKIT_FORCE_SANDBOX=1.

The crash appears to be specific to the Flatpak sandbox's interaction with the WebKit renderer when loading the Mainsail interface on this particular hardware/software combination. The AppImage version has not yet been tested, but the web browser workaround is stable.

*Originally created by @SergeiVaidie on 3/12/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-rc2 (Flatpak version from Flathub) ### Operating System (OS) Linux ### OS Version Linux Mint 22.3 "Zena" (based on Ubuntu 24.04) ### Additional system information CPU: 11th Gen Intel© Core™ i5-1135G7 @ 2.40GHz × 4 RAM: 32 GB Graphics Hardware: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (integrated) Graphics Drivers: Mesa 25.2.8-0ubuntu0.24.04.1 (confirmed via glxinfo) Desktop Environment: Cinnamon 6.6.7 (X11 session) ### Printer Anycubic Kobra S1 Combo with Rinkhals ### How to reproduce 1. Install the Flatpak version of OrcaSlicer on a compatible Linux system. 2. Configure a printer with a valid Moonraker connection (e.g., 192.168.1.51). 3. Open OrcaSlicer and click on the Device tab. 4. Observe the Mainsail interface starting to load in the panel, followed by the immediate and silent crash of the whole application. ### Actual results The OrcaSlicer Flatpak version (io.github.orcaslicer.OrcaSlicer) crashes consistently and silently when switching to the Device tab. The Mainsail web interface begins to load, and then the entire application closes without an error dialogue. The application runs fine on the Prepare and Preview tabs. ### Expected results The Device tab should load and display the Mainsail (or Fluidd) interface correctly, allowing for printer control and monitoring, just as it does in a regular web browser. ### Project file & Debug log uploads Debug log --> [debug_Thu_Mar_12_23_36_06_2.log.0.zip](https://github.com/user-attachments/files/25954877/debug_Thu_Mar_12_23_36_06_2.log.0.zip) ### Checklist of files to include - [x] Log file - [ ] Project file ### Anything else? I have conducted extensive troubleshooting with a user facing this exact issue and can confirm the following attempted fixes did not resolve the crash: 1. Ensuring the correct Moonraker port (:7125) is used in the printer host configuration. 2. Setting WEBKIT_DISABLE_DMABUF_RENDERER=1 environment variable. 3. Unsetting the DRI_PRIME environment variable in the Flatpak. 4. Forcing the Flatpak to use only the X11 socket (--socket=x11 --nosocket=wayland). 5. Forcing software rendering with LIBGL_ALWAYS_SOFTWARE=1. 6. Forcing an alternative WebKit backend with WEBKIT_FORCE_SANDBOX=1. The crash appears to be specific to the Flatpak sandbox's interaction with the WebKit renderer when loading the Mainsail interface on this particular hardware/software combination. The AppImage version has not yet been tested, but the web browser workaround is stable.

MrUnknownDE closed this issue

2026-04-05 16:20:01 +02:00

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#338