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 crashes (SIGABRT) on plugin hot-reload: "Tried to show lockscreen surfaces without active lock"
Reported by houz42 · filed Sep 2, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9654 (R-1096). 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 aborted (SIGABRT) twice in a row (crash loop) when a plugin under
~/.config/omarchy/plugins/ was updated/reloaded while the shell's lock service
was recovering a "stranded" lock from a previous instance.
Evidence
Log immediately preceding both crashes (Quickshell's own crash log,
~/.cache/quickshell/crashes/<run-id>/report.txt):
omarchy lock 2026-09-01T02:49:17.086Z lock-stranded: recovering
omarchy lock 2026-09-01T02:49:17.086Z lock-requested
omarchy lock 2026-09-01T02:49:17.086Z lock-pending: screen-stabilizing
FATAL: Tried to show lockscreen surfaces without active lock
Backtrace (both crashes identical):
abort() <- QDebug::~QDebug() <- quickshell <- QQmlPropertyPrivate::write
<- ... <- QQmlTimer::event <- QCoreApplication::exec
quickshell 0.3.1-1, qt6-base/qt6-declarative 6.11.2, Omarchy 4.0.1.
Steps to reproduce
- Have Quickshell running with a session lock in a "stranded" state (e.g.
from a prior restart).
2. Trigger a config/plugin hot-reload (e.g. update a plugin under
~/.config/omarchy/plugins/, causing the file watcher to fire).
3. The lock-recovery sequence races the reload; Quickshell shows lock
surfaces before the compositor has confirmed the lock, hitting its own
fatal invariant check and aborting.
4. Quickshell auto-restarts, immediately hits the same race, crashes again
within 10s, and gives up restarting ("Not restarting to avoid a crash
loop") — leaving the shell dead until manually relaunched.
Expected
The lock-recovery path should wait for lock confirmation before requesting
lock surfaces, or should not race a concurrent shell reload.
Filed by Claude Sonnet 5 via Claude Code.
View raw text
## What happened
Quickshell aborted (SIGABRT) twice in a row (crash loop) when a plugin under
~/.config/omarchy/plugins/ was updated/reloaded while the shell's lock service
was recovering a "stranded" lock from a previous instance.
## Evidence
Log immediately preceding both crashes (Quickshell's own crash log,
~/.cache/quickshell/crashes/<run-id>/report.txt):
omarchy lock 2026-09-01T02:49:17.086Z lock-stranded: recovering
omarchy lock 2026-09-01T02:49:17.086Z lock-requested
omarchy lock 2026-09-01T02:49:17.086Z lock-pending: screen-stabilizing
FATAL: Tried to show lockscreen surfaces without active lock
Backtrace (both crashes identical):
abort() <- QDebug::~QDebug() <- quickshell <- QQmlPropertyPrivate::write
<- ... <- QQmlTimer::event <- QCoreApplication::exec
quickshell 0.3.1-1, qt6-base/qt6-declarative 6.11.2, Omarchy 4.0.1.
## Steps to reproduce
1. Have Quickshell running with a session lock in a "stranded" state (e.g.
from a prior restart).
2. Trigger a config/plugin hot-reload (e.g. update a plugin under
~/.config/omarchy/plugins/, causing the file watcher to fire).
3. The lock-recovery sequence races the reload; Quickshell shows lock
surfaces before the compositor has confirmed the lock, hitting its own
fatal invariant check and aborting.
4. Quickshell auto-restarts, immediately hits the same race, crashes again
within 10s, and gives up restarting ("Not restarting to avoid a crash
loop") — leaving the shell dead until manually relaunched.
## Expected
The lock-recovery path should wait for lock confirmation before requesting
lock surfaces, or should not race a concurrent shell reload.
Filed by Claude Sonnet 5 via Claude Code.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.