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-289GitHub issuePublicDecided· Out of scope

Shell SIGSEGV (Repeater delegate use-after-free) under NetworkManager AP churn on quickshell 0.3.1

Reported by Dandroid-D · filed Sep 20, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Shell SIGSEGV (Repeater delegate use-after-free) under NetworkManager AP churn on quickshell 0.3.1revision 1 · captured 2026-09-28 21:23 UTC via poll

Crash summary: The Omarchy shell (quickshell -n -p /usr/share/omarchy/shell) hard-crashed with SIGSEGV (2026-09-20, single occurrence) during a bar click while NetworkManager access-point objects were churning heavily during scans. Backtrace: QQuickMouseArea::mouseReleaseEvent → JS handler → QQuickRepeater::setModel → regenerate() → delegate incubation → typeof name lookup hits freed memory in libQt6QmlModels (QQmlDelegateModel data). Classic model-churn use-after-free; the 19.7 MB crash log is dominated by NM AP add/update/remove events.

Environment: quickshell 0.3.1-1 (Arch extra, latest), Qt 6.11.2, omarchy 4.0.4-1, stock shell (pacman -Qkk omarchy → 0 altered files), Hyprland + amdgpu.

Handling worked: omarchy-launch-shell relaunched the shell ~2 min later and omarchy-crash-watch announced it — no manual intervention needed. Just filing so the crash class is tracked on the Omarchy side.

Upstream report with full backtrace excerpt: https://github.com/quickshell-mirror/quickshell/issues/1164

Post-v0.3.1 quickshell master contains plausible fixes (92cb8909 disconnect deleteLater'd QObjects, c6a51609 scriptmodel native-type comparison). Once quickshell cuts a release carrying them, a version bump here would close this out. Workaround in the meantime: quickshell-git from the AUR.

View raw text
**Crash summary:** The Omarchy shell (`quickshell -n -p /usr/share/omarchy/shell`) hard-crashed with SIGSEGV (2026-09-20, single occurrence) during a bar click while NetworkManager access-point objects were churning heavily during scans. Backtrace: `QQuickMouseArea::mouseReleaseEvent` → JS handler → `QQuickRepeater::setModel` → `regenerate()` → delegate incubation → `typeof` name lookup hits freed memory in `libQt6QmlModels` (QQmlDelegateModel data). Classic model-churn use-after-free; the 19.7 MB crash log is dominated by NM AP add/update/remove events.

**Environment:** quickshell 0.3.1-1 (Arch `extra`, latest), Qt 6.11.2, omarchy 4.0.4-1, stock shell (`pacman -Qkk omarchy` → 0 altered files), Hyprland + amdgpu.

**Handling worked:** `omarchy-launch-shell` relaunched the shell ~2 min later and `omarchy-crash-watch` announced it — no manual intervention needed. Just filing so the crash class is tracked on the Omarchy side.

**Upstream report with full backtrace excerpt:** https://github.com/quickshell-mirror/quickshell/issues/1164

Post-v0.3.1 quickshell master contains plausible fixes (`92cb8909` disconnect deleteLater'd QObjects, `c6a51609` scriptmodel native-type comparison). Once quickshell cuts a release carrying them, a version bump here would close this out. Workaround in the meantime: `quickshell-git` from the AUR.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 16:25 UTC