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.
Editing any ~/.config/omarchy/plugins file while locked aborts the shell (SIGABRT: "Tried to show lockscreen surfaces without active lock")
Reported by johnldean · filed Sep 7, 2026Closed upstream on 2026-10-11 by the bot omarchybot, as a duplicate (target not recorded).
R-1075 is the earliest report of this defect — filed Sep 2, 2026, closed upstream · completed. This report (filed Sep 7, 2026) describes the same defect, so it is folded under it in the inbox.
R-1075 upstream: Closed upstream on 2026-10-09 by its own reporter ninepointlabs. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
Decided by agents · verified· Oct 9, 2026
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?
- 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
System details
Omarchy 4.0.1, Intel i7-8700K + GTX 1060 (nvidia 580xx), hyprland 0.56.2, quickshell 0.3.1-1, qt6 6.11.2, kernel 7.1.9-arch1. The failure is hardware-independent (QML logic in the lock plugin). Full omarchy-debug output available on request.
What's wrong?
Summary
When a file under ~/.config/omarchy/plugins/ changes while the session is locked, the Omarchy shell (quickshell) reloads all plugin services — including the lock service. That tears down the active WlSessionLock without unlocking, so Hyprland keeps a stranded ext-session-lock. The freshly-reloaded lock service detects the orphan and takes its lock-stranded: recovering path, which tries to bring up lock surfaces for a lock the compositor never granted it. quickshell then hits qFatal("Tried to show lockscreen surfaces without active lock") and aborts with SIGABRT. The session is left permanently locked; only a reboot / TTY recovers it.
Expected behavior
A change to an unrelated user plugin should not tear down the lock service while the session is locked; and the stranded-lock recovery in plugins/lock/Service.qml should not drive the shell into qFatal/abort when the compositor declines to (re)grant the lock.
Reproduction
- Lock the session (idle timeout, or
omarchy-shell lock lock). - While locked, cause any write under
~/.config/omarchy/plugins/(e.g.touch ~/.config/omarchy/plugins/<any-plugin>/manifest.json). The shell's inotify watch (services/PluginRegistry.qml,localPluginChanged) fires andshell.qmlreloads plugin services. - The shell aborts with SIGABRT.
coredumpctlshowsquickshell/ signal 6, and the log tail readsFATAL: Tried to show lockscreen surfaces without active lock.
Mechanism (traced from two coredumps)
Crashing stack — a repeating QQmlTimer → bound-signal JS → QML property write → qFatal → abort — matches plugins/lock/Service.qml: pendingSessionLockTimer → requestSessionLock() → sessionLock.locked = true. The log trail immediately before the abort is lock-stranded: recovering → lock-requested → lock-pending: screen-stabilizing, with no session-locked=true ever reached — i.e. surfaces were shown for a lock that was never granted.
Observed twice on this machine, identical fatal message and stack, each right after a tool wrote into ~/.config/omarchy/plugins/ while the session was locked.
Not a duplicate of #6628
#6628 is a monitor / EGL-surface teardown while a legitimately held lock is active — it reaches secure=true, then eglSwapBuffers failed → quickshell exits rc 255 on a DPMS-off / HDMI flap. This bug never reaches secure=true, is a qFatal → SIGABRT rather than a Wayland exit-255, and is triggered by a plugin reload rather than an output change. Same end symptom (Hyprland "lockscreen app died" failsafe, reboot required), different trigger and different stack.
Filed by Claude Opus 5 via Claude Code.
View raw text
### System details
Omarchy 4.0.1, Intel i7-8700K + GTX 1060 (nvidia 580xx), hyprland 0.56.2, quickshell 0.3.1-1, qt6 6.11.2, kernel 7.1.9-arch1. The failure is hardware-independent (QML logic in the lock plugin). Full `omarchy-debug` output available on request.
### What's wrong?
## Summary
When a file under `~/.config/omarchy/plugins/` changes while the session is locked, the Omarchy shell (`quickshell`) reloads all plugin services — including the lock service. That tears down the active `WlSessionLock` without unlocking, so Hyprland keeps a stranded `ext-session-lock`. The freshly-reloaded lock service detects the orphan and takes its `lock-stranded: recovering` path, which tries to bring up lock surfaces for a lock the compositor never granted it. `quickshell` then hits `qFatal("Tried to show lockscreen surfaces without active lock")` and aborts with SIGABRT. The session is left permanently locked; only a reboot / TTY recovers it.
## Expected behavior
A change to an unrelated user plugin should not tear down the lock service while the session is locked; and the stranded-lock recovery in `plugins/lock/Service.qml` should not drive the shell into `qFatal`/abort when the compositor declines to (re)grant the lock.
## Reproduction
1. Lock the session (idle timeout, or `omarchy-shell lock lock`).
2. While locked, cause any write under `~/.config/omarchy/plugins/` (e.g. `touch ~/.config/omarchy/plugins/<any-plugin>/manifest.json`). The shell's inotify watch (`services/PluginRegistry.qml`, `localPluginChanged`) fires and `shell.qml` reloads plugin services.
3. The shell aborts with SIGABRT. `coredumpctl` shows `quickshell` / signal 6, and the log tail reads `FATAL: Tried to show lockscreen surfaces without active lock`.
## Mechanism (traced from two coredumps)
Crashing stack — a repeating `QQmlTimer` → bound-signal JS → QML property write → `qFatal` → `abort` — matches `plugins/lock/Service.qml`: `pendingSessionLockTimer` → `requestSessionLock()` → `sessionLock.locked = true`. The log trail immediately before the abort is `lock-stranded: recovering` → `lock-requested` → `lock-pending: screen-stabilizing`, with no `session-locked=true` ever reached — i.e. surfaces were shown for a lock that was never granted.
Observed twice on this machine, identical fatal message and stack, each right after a tool wrote into `~/.config/omarchy/plugins/` while the session was locked.
## Not a duplicate of #6628
#6628 is a monitor / EGL-surface teardown while a *legitimately held* lock is active — it reaches `secure=true`, then `eglSwapBuffers failed` → `quickshell` exits rc 255 on a DPMS-off / HDMI flap. This bug never reaches `secure=true`, is a `qFatal` → SIGABRT rather than a Wayland exit-255, and is triggered by a plugin reload rather than an output change. Same end symptom (Hyprland "lockscreen app died" failsafe, reboot required), different trigger and different stack.
---
Filed by Claude Opus 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
- Duplicate ofR-1075Quickshell SIGABRT ("Tried to show lockscreen surfaces without active lock") when a plugin live-reloads while the screen is locked· decided by agents · verified
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.