Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
quickshell crash (SIGSEGV) during PipeWire audio device switch — QML Repeater binding update
Reported by kczimm · filed Sep 1, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6952 (R-1843). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
Quickshell 0.3.1-1 crashed with SIGSEGV at 12:32:51 CDT while running the Omarchy shell config (-p /usr/share/omarchy/shell). The signal was self-inflicted (si_code: SI_TKILL) — quickshell's crash handler or a Qt assertion raised SIGSEGV, not a hardware memory fault.
Trigger
A Bluetooth audio device disconnected, causing PipeWire to tear down and re-enumerate devices. The default sink switched from bluez_output.08_DF_1F_35_07_90.1 to alsa_output.pci-0000_01_00.1.hdmi-stereo. The crash occurred ~6 seconds after the initial PipeWire error (code -14).
Stack trace
The crashing thread was in a QQuickRepeater::setModel → regenerate cycle, incubating a new QML item. During module evaluation, TypeofName::call resolved a property and the engine hit an invalid state:
#0 raise (libc.so.6)
#2 quickshell + 0x124389
#4 QV4::QObjectWrapper::getQmlProperty
#7 QV4::Runtime::TypeofName::call
#13 QV4::Module::evaluate
#16 QQmlIncubatorPrivate::incubate
#19 QQuickRepeater::regenerate
#20 QQuickRepeater::setModel
#22 QQmlPropertyPrivate::write
#26 QQmlBinding::slowWriteSystem details
- Omarchy 4.0.2-1, Arch Linux rolling
- Quickshell 0.3.1-1, Qt 6.11.2
- NVIDIA GPU (10de:2d04), nvidia-drm driver
- Memory healthy: 7.6 GB used / 15 GB total, no OOM
- One-off crash — no previous quickshell crashes in coredumpctl
- Full crash report saved at
/home/kevin/.cache/quickshell/crashes/0x2cu0pkt/
Notes
This is a one-off crash, not a repeated pattern. It was triggered by a Bluetooth headset disconnect causing a PipeWire device switch. The QML binding update in the audio widget likely hit an invalid state during repeater model regeneration.
View raw text
## What happened Quickshell 0.3.1-1 crashed with SIGSEGV at 12:32:51 CDT while running the Omarchy shell config (`-p /usr/share/omarchy/shell`). The signal was self-inflicted (`si_code: SI_TKILL`) — quickshell's crash handler or a Qt assertion raised SIGSEGV, not a hardware memory fault. ## Trigger A Bluetooth audio device disconnected, causing PipeWire to tear down and re-enumerate devices. The default sink switched from `bluez_output.08_DF_1F_35_07_90.1` to `alsa_output.pci-0000_01_00.1.hdmi-stereo`. The crash occurred ~6 seconds after the initial PipeWire error (code -14). ## Stack trace The crashing thread was in a `QQuickRepeater::setModel` → `regenerate` cycle, incubating a new QML item. During module evaluation, `TypeofName::call` resolved a property and the engine hit an invalid state: ``` #0 raise (libc.so.6) #2 quickshell + 0x124389 #4 QV4::QObjectWrapper::getQmlProperty #7 QV4::Runtime::TypeofName::call #13 QV4::Module::evaluate #16 QQmlIncubatorPrivate::incubate #19 QQuickRepeater::regenerate #20 QQuickRepeater::setModel #22 QQmlPropertyPrivate::write #26 QQmlBinding::slowWrite ``` ## System details - Omarchy 4.0.2-1, Arch Linux rolling - Quickshell 0.3.1-1, Qt 6.11.2 - NVIDIA GPU (10de:2d04), nvidia-drm driver - Memory healthy: 7.6 GB used / 15 GB total, no OOM - One-off crash — no previous quickshell crashes in coredumpctl - Full crash report saved at `/home/kevin/.cache/quickshell/crashes/0x2cu0pkt/` ## Notes This is a one-off crash, not a repeated pattern. It was triggered by a Bluetooth headset disconnect causing a PipeWire device switch. The QML binding update in the audio widget likely hit an invalid state during repeater model regeneration.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.