Device Tab crashes with SEGV in libwebkit2gtk on Wayland (Fedora 43 KDE) #314

New Issue

MrUnknownDE · 2026-04-05T16:19:49+02:00

MrUnknownDE commented

2026-04-05 16:19:49 +02:00

Originally created by @3DManiax on 3/15/2026

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.2-rc2

Operating System (OS)

Linux

OS Version

Fedora 43 KDE Plasma Edition

Additional system information

Intel® Core™ Ultra 7 155H
96GB RAM

Printer

Qidi Q2

How to reproduce

Device Tab crashes with SEGV in libwebkit2gtk on Wayland (Fedora 43 KDE)

Summary

Opening the Device tab with a configured Qidi Q2 printer causes an immediate crash (SIGSEGV) in libwebkit2gtk-4.1. This is a regression – OrcaSlicer 2.3.1 does not exhibit this behaviour with identical configuration.

Three separate bugs were identified:

SEGV in libwebkit2gtk when opening the Device tab under Wayland
Endless get_version polling loop without timeout or error handling
Shipped system profile fdm_qidi_x3_common.json contains keys that were already removed

Environment


OS	Fedora 43 KDE
Display Server	Wayland
OrcaSlicer	2.3.2-rc2 (Flatpak `io.github.orcaslicer.OrcaSlicer`)
Printer	Qidi Q2 (Moonraker/Klipper)
Installation	Flatpak, fresh config (no migration from 2.3.1)
Printer Firmware	QIDI Q2 v1.1.1 (Klipper/Moonraker, version string reports "?" via API)
Printer OS	Debian GNU/Linux 11 (bullseye), Kernel 5.10.160, aarch64
Moonraker API	1.4.0

Steps to Reproduce

Install OrcaSlicer 2.3.2-rc2 as Flatpak on Fedora 43 KDE (Wayland) with no prior configuration
Configure Qidi Q2 with printer IP
Open the Device tab
Moonraker UI briefly appears showing "Klippy not connected"
UI freezes → application crashes

Actual Results

OrcaSlicer crashes with SIGSEGV in libwebkit2gtk-4.1.so.0.19.8.

The log shows an endless polling loop prior to the crash, firing every 2 seconds with no timeout:

get_version, get_version not supported, return 00.00.00.00!
get_version, get_version not supported, return 00.00.00.00!
... (repeats for several minutes until crash)

The crash itself:

Signal: 11 (SEGV)
Crash location: libwebkit2gtk-4.1.so.0.19.8 + 0xf33372

Full stack trace (from coredump, 85.6 MB available on request):

#0  libwebkit2gtk-4.1.so.0.19.8 + 0xf33372
#1  libwebkit2gtk-4.1.so.0.19.8 + 0xdacafb
#2  libwebkit2gtk-4.1.so.0.19.8 + 0xecabeb
#3  libwebkit2gtk-4.1.so.0.19.8 + 0x837e14
#4  libwebkit2gtk-4.1.so.0.19.8 + 0xcd1e6c
#5  libwebkit2gtk-4.1.so.0.19.8 + 0xe01640
#6  libwebkit2gtk-4.1.so.0.19.8 + 0x876109
#7  libwebkit2gtk-4.1.so.0.19.8 + 0xcc9950
#8  libwebkit2gtk-4.1.so.0.19.8 + 0xcc9b47
#9  libwebkit2gtk-4.1.so.0.19.8 + 0xcc9fcd
#10 libjavascriptcoregtk-4.1.so.0.9.10 + 0x1861875
#11 libjavascriptcoregtk-4.1.so.0.9.10 + 0x191e59d
#12 libjavascriptcoregtk-4.1.so.0.9.10 + 0x191d6c1
#13 libglib-2.0.so.0.8400.4 + 0x62bba
#14 libglib-2.0.so.0.8400.4 + 0x64ed7
#15 libglib-2.0.so.0.8400.4 + 0x659d7
#16 libgtk-3.so.0.2419.32 + 0x3ab565
#17 /app/lib/libwx_gtk3u_core-3.1.so + 0x6d9245
#18 /app/lib/libwx_baseu-3.1.so + 0x115d3a
#19 /app/lib/libwx_baseu-3.1.so + 0xd47c3
#20 /app/lib/libwx_baseu-3.1.so + 0x16cf69
#21 /app/bin/orca-slicer + 0x1a00f0b
#22 /app/bin/orca-slicer + 0xc6c273
#23 /app/bin/orca-slicer + 0xb725d7

Expected Results

Device tab opens and displays the Moonraker interface without crashing. get_version polling should have a proper timeout and error handling.

Not Reproducible With

OrcaSlicer 2.3.1 (Flatpak io.github.softfever.OrcaSlicer) – identical printer configuration, same system.

Additional Bug: Shipped system profile contains removed keys

The following error appears on startup even with a fresh installation:

The config system/Qidi/machine/fdm_qidi_x3_common.json contains incorrect keys:
filament_tower_interface_pre_extrusion_dist,
filament_tower_interface_pre_extrusion_length,
filament_tower_interface_print_temp,
filament_tower_interface_purge_volume,
filament_tower_ironing_area,
which were removed

This profile is shipped with RC2 and not user-generated, indicating the bundled system profiles were not updated before the release candidate was published.

Notes

libwebkit2gtk-4.1.so.0.19.8 and libjavascriptcoregtk-4.1.so.0.9.10 are loaded without build-id (host libraries, not bundled with the Flatpak)
The endless polling loop may be the root cause driving WebKit into the crash
Full coredump (85.6 MB) available on request
The printer itself reports "?" for both klipper and moonraker version strings
This appears to be the direct trigger for the endless get_version polling loop
OrcaSlicer 2.3.1 handles this gracefully; 2.3.2-rc2 does not
- OrcaSlicer 2.3.1 logs "get_version not supported" exactly once per session,
  then continues normally (verified across multiple sessions in logs).
OrcaSlicer 2.3.2-rc2 retries every ~2 seconds indefinitely with no exit
condition, eventually causing the WebKit SEGV.
This confirms the regression is in the version-polling logic introduced
between 2.3.1 and 2.3.2-rc2.

Actual results

OrcaSlicer crashes immediately with SIGSEGV in libwebkit2gtk-4.1.so.0.19.8.
The Moonraker UI briefly appears, then the UI freezes and the application terminates.

Signal: 11 (SEGV)
Crash location: libwebkit2gtk-4.1.so.0.19.8 + 0xf33372
Full stack trace available via coredump (85.6 MB, can be provided on request).

Expected results

Device tab opens and displays the Moonraker interface without crashing.

Project file & Debug log uploads

orca_rc2_log.zip

Checklist of files to include

Log file
Project file

Anything else?

No response

*Originally created by @3DManiax on 3/15/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-rc2 ### Operating System (OS) Linux ### OS Version Fedora 43 KDE Plasma Edition ### Additional system information - Intel® Core™ Ultra 7 155H - 96GB RAM ### Printer Qidi Q2 ### How to reproduce ## Device Tab crashes with SEGV in libwebkit2gtk on Wayland (Fedora 43 KDE) ### Summary Opening the **Device tab** with a configured Qidi Q2 printer causes an immediate crash (SIGSEGV) in `libwebkit2gtk-4.1`. This is a **regression** – OrcaSlicer 2.3.1 does not exhibit this behaviour with identical configuration. Three separate bugs were identified: 1. SEGV in `libwebkit2gtk` when opening the Device tab under Wayland 2. Endless `get_version` polling loop without timeout or error handling 3. Shipped system profile `fdm_qidi_x3_common.json` contains keys that were already removed --- ### Environment | | | |---|---| | OS | Fedora 43 KDE | | Display Server | Wayland | | OrcaSlicer | 2.3.2-rc2 (Flatpak `io.github.orcaslicer.OrcaSlicer`) | | Printer | Qidi Q2 (Moonraker/Klipper) | | Installation | Flatpak, **fresh config** (no migration from 2.3.1) | | Printer Firmware | QIDI Q2 v1.1.1 (Klipper/Moonraker, version string reports "?" via API) | | Printer OS | Debian GNU/Linux 11 (bullseye), Kernel 5.10.160, aarch64 | | Moonraker API | 1.4.0 | --- ### Steps to Reproduce 1. Install OrcaSlicer 2.3.2-rc2 as Flatpak on Fedora 43 KDE (Wayland) with **no prior configuration** 2. Configure Qidi Q2 with printer IP 3. Open the **Device** tab 4. Moonraker UI briefly appears showing "Klippy not connected" 5. UI freezes → application crashes --- ### Actual Results OrcaSlicer crashes with SIGSEGV in `libwebkit2gtk-4.1.so.0.19.8`. The log shows an **endless polling loop** prior to the crash, firing every 2 seconds with no timeout: ``` get_version, get_version not supported, return 00.00.00.00! get_version, get_version not supported, return 00.00.00.00! ... (repeats for several minutes until crash) ``` The crash itself: ``` Signal: 11 (SEGV) Crash location: libwebkit2gtk-4.1.so.0.19.8 + 0xf33372 ``` Full stack trace (from coredump, 85.6 MB available on request): ``` #0 libwebkit2gtk-4.1.so.0.19.8 + 0xf33372 #1 libwebkit2gtk-4.1.so.0.19.8 + 0xdacafb #2 libwebkit2gtk-4.1.so.0.19.8 + 0xecabeb #3 libwebkit2gtk-4.1.so.0.19.8 + 0x837e14 #4 libwebkit2gtk-4.1.so.0.19.8 + 0xcd1e6c #5 libwebkit2gtk-4.1.so.0.19.8 + 0xe01640 #6 libwebkit2gtk-4.1.so.0.19.8 + 0x876109 #7 libwebkit2gtk-4.1.so.0.19.8 + 0xcc9950 #8 libwebkit2gtk-4.1.so.0.19.8 + 0xcc9b47 #9 libwebkit2gtk-4.1.so.0.19.8 + 0xcc9fcd #10 libjavascriptcoregtk-4.1.so.0.9.10 + 0x1861875 #11 libjavascriptcoregtk-4.1.so.0.9.10 + 0x191e59d #12 libjavascriptcoregtk-4.1.so.0.9.10 + 0x191d6c1 #13 libglib-2.0.so.0.8400.4 + 0x62bba #14 libglib-2.0.so.0.8400.4 + 0x64ed7 #15 libglib-2.0.so.0.8400.4 + 0x659d7 #16 libgtk-3.so.0.2419.32 + 0x3ab565 #17 /app/lib/libwx_gtk3u_core-3.1.so + 0x6d9245 #18 /app/lib/libwx_baseu-3.1.so + 0x115d3a #19 /app/lib/libwx_baseu-3.1.so + 0xd47c3 #20 /app/lib/libwx_baseu-3.1.so + 0x16cf69 #21 /app/bin/orca-slicer + 0x1a00f0b #22 /app/bin/orca-slicer + 0xc6c273 #23 /app/bin/orca-slicer + 0xb725d7 ``` --- ### Expected Results Device tab opens and displays the Moonraker interface without crashing. `get_version` polling should have a proper timeout and error handling. --- ### Not Reproducible With OrcaSlicer 2.3.1 (Flatpak `io.github.softfever.OrcaSlicer`) – identical printer configuration, same system. --- ### Additional Bug: Shipped system profile contains removed keys The following error appears on startup even with a **fresh installation**: ``` The config system/Qidi/machine/fdm_qidi_x3_common.json contains incorrect keys: filament_tower_interface_pre_extrusion_dist, filament_tower_interface_pre_extrusion_length, filament_tower_interface_print_temp, filament_tower_interface_purge_volume, filament_tower_ironing_area, which were removed ``` This profile is **shipped with RC2** and not user-generated, indicating the bundled system profiles were not updated before the release candidate was published. --- ### Notes - `libwebkit2gtk-4.1.so.0.19.8` and `libjavascriptcoregtk-4.1.so.0.9.10` are loaded **without build-id** (host libraries, not bundled with the Flatpak) - The endless polling loop may be the root cause driving WebKit into the crash - Full coredump (85.6 MB) available on request - The printer itself reports "?" for both klipper and moonraker version strings - This appears to be the direct trigger for the endless get_version polling loop - OrcaSlicer 2.3.1 handles this gracefully; 2.3.2-rc2 does not - - OrcaSlicer 2.3.1 logs "get_version not supported" exactly once per session, then continues normally (verified across multiple sessions in logs). - OrcaSlicer 2.3.2-rc2 retries every ~2 seconds indefinitely with no exit condition, eventually causing the WebKit SEGV. - This confirms the regression is in the version-polling logic introduced between 2.3.1 and 2.3.2-rc2. ### Actual results OrcaSlicer crashes immediately with SIGSEGV in libwebkit2gtk-4.1.so.0.19.8. The Moonraker UI briefly appears, then the UI freezes and the application terminates. Signal: 11 (SEGV) Crash location: libwebkit2gtk-4.1.so.0.19.8 + 0xf33372 Full stack trace available via coredump (85.6 MB, can be provided on request). ### Expected results Device tab opens and displays the Moonraker interface without crashing. ### Project file & Debug log uploads [orca_rc2_log.zip](https://github.com/user-attachments/files/26004616/orca_rc2_log.zip) ### Checklist of files to include - [x] Log file - [ ] Project file ### Anything else? _No response_

MrUnknownDE closed this issue

2026-04-05 16:19:49 +02:00

MrUnknownDE added the duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate labels 2026-04-05 16:19:49 +02:00

Sign in to join this conversation.

No Label duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate duplicate

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#314