Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4765GitHub issuePublicReceived

Restarting audio services crashes QuickShell in QQuickRepeater::regenerate

Reported by kstimpson85 · filed Aug 30, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6952 (R-1843). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Restarting audio services crashes QuickShell in QQuickRepeater::regeneraterevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

Running omarchy restart audio caused the Omarchy QuickShell process to crash with SIGSEGV. QuickShell restarted automatically, so no user data was lost.

The journal shows the audio restart stopping PipeWire, WirePlumber, and PipeWire PulseAudio. During QuickShell's PipeWire disconnect/reconnect handling, QuickShell crashed while regenerating a QML Repeater.

Crash run ID: pvsrllkt

Steps to reproduce

  1. Run omarchy restart audio.
  2. Observe the Omarchy shell crash and automatically restart.

This was observed once. I have not repeatedly reproduced it to avoid unnecessarily disrupting the desktop session.

Expected behavior

Audio services restart without terminating the Omarchy shell.

Actual behavior

QuickShell receives SIGSEGV and restarts.

Relevant timeline

17:18:11 omarchy-restart-audio invoked
17:18:11 PipeWire, WirePlumber, and PipeWire PulseAudio stopped
17:18:11 QuickShell reported PipeWire connection error
17:18:11 PipeWire services restarted
17:18:11 QuickShell destroyed and recreated its PipeWire node model
17:18:11 QuickShell crashed with SIGSEGV

Relevant stack frames

libQt6QmlModels.so.6
QV4::QObjectWrapper::getQmlProperty
QV4::Module::evaluate
QQmlObjectCreator::createInstance
QQmlIncubatorPrivate::incubate
QQuickRepeater::regenerate
QQuickRepeater::setModel
QQmlBinding::update
QQmlTimer::event

The shipped audio panel already snapshots PipeWire-backed lists before feeding them to Repeater, with a comment explaining that rebuilding a Repeater during PipeWire node removal has previously crashed QuickShell. This crash indicates that the current protection may not cover every model update during a full audio-service restart.

System details

  • Omarchy: 4.0.1-1
  • QuickShell: 0.3.1-1
  • Qt: 6.11.2
  • PipeWire: 1.6.8
  • WirePlumber: 0.5.15
  • Kernel: 7.1.9-arch1-2
  • Shell config: /usr/share/omarchy/shell/shell.qml
  • Hardware: MacBookPro13,3, Intel HD 530 + AMD Radeon Pro 455

The complete local QuickShell report is stored at:

~/.cache/quickshell/crashes/pvsrllkt/report.txt

A standard omarchy-debug --no-sudo --print report was also collected successfully.

Filed by GPT-5 via Codex.

View raw text
## What happened

Running `omarchy restart audio` caused the Omarchy QuickShell process to crash with SIGSEGV. QuickShell restarted automatically, so no user data was lost.

The journal shows the audio restart stopping PipeWire, WirePlumber, and PipeWire PulseAudio. During QuickShell's PipeWire disconnect/reconnect handling, QuickShell crashed while regenerating a QML `Repeater`.

Crash run ID: `pvsrllkt`

## Steps to reproduce

1. Run `omarchy restart audio`.
2. Observe the Omarchy shell crash and automatically restart.

This was observed once. I have not repeatedly reproduced it to avoid unnecessarily disrupting the desktop session.

## Expected behavior

Audio services restart without terminating the Omarchy shell.

## Actual behavior

QuickShell receives SIGSEGV and restarts.

## Relevant timeline

```text
17:18:11 omarchy-restart-audio invoked
17:18:11 PipeWire, WirePlumber, and PipeWire PulseAudio stopped
17:18:11 QuickShell reported PipeWire connection error
17:18:11 PipeWire services restarted
17:18:11 QuickShell destroyed and recreated its PipeWire node model
17:18:11 QuickShell crashed with SIGSEGV
```

## Relevant stack frames

```text
libQt6QmlModels.so.6
QV4::QObjectWrapper::getQmlProperty
QV4::Module::evaluate
QQmlObjectCreator::createInstance
QQmlIncubatorPrivate::incubate
QQuickRepeater::regenerate
QQuickRepeater::setModel
QQmlBinding::update
QQmlTimer::event
```

The shipped audio panel already snapshots PipeWire-backed lists before feeding them to `Repeater`, with a comment explaining that rebuilding a Repeater during PipeWire node removal has previously crashed QuickShell. This crash indicates that the current protection may not cover every model update during a full audio-service restart.

## System details

- Omarchy: `4.0.1-1`
- QuickShell: `0.3.1-1`
- Qt: `6.11.2`
- PipeWire: `1.6.8`
- WirePlumber: `0.5.15`
- Kernel: `7.1.9-arch1-2`
- Shell config: `/usr/share/omarchy/shell/shell.qml`
- Hardware: MacBookPro13,3, Intel HD 530 + AMD Radeon Pro 455

The complete local QuickShell report is stored at:

`~/.cache/quickshell/crashes/pvsrllkt/report.txt`

A standard `omarchy-debug --no-sudo --print` report was also collected successfully.

Filed by GPT-5 via Codex.

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.