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 (Omarchy shell) aborts: "Tried to show lockscreen surfaces without active lock"
Reported by lama7 · 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
Description
The Omarchy shell (quickshell) crashes with SIGABRT when lockscreen code attempts to show surfaces without an active lock session.
Trigger
Logged 2 seconds before crash:
FATAL: Tried to show lockscreen surfaces without active lockStack Trace (symbolized)
#0 raise (libc.so.6)
#1 abort (libc.so.6)
#2 QMessageLogger::fatal() (libQt6Core.so.6)
#3 QDebug::~QDebug() (libQt6Core.so.6)
#4 quickshell + 0x832b3 (omarchy shell QML)
#5 quickshell + 0x2240c2 (omarchy shell QML)
#6 QQmlPropertyPrivate::write() (libQt6Qml.so.6)
#7 QV4::QObjectWrapper::setProperty() (libQt6Qml.so.6)
... QML timer event \u2192 bound signal evaluation \u2192 property write \u2192 abortSystem
Omarchy: 4.0.2
quickshell: 0.3.1 (Arch Linux)
Qt: 6.11.2
GPU: AMD amdgpu 3.64.0 (1002:15d8)Reproduction
Unknown exact steps \u2014 occurred during normal desktop use. Likely related to lock/unlock cycle, idle timeout, or lid close/open triggering a race in lockscreen state management.
Impact
Shell auto-restarts (~1s downtime), no user data lost. Likely to recur under same conditions.
Debug Info
omarchy versionoutputomarchy debug --no-sudo --print(attaches/tmp/omarchy-debug.log)
Filed by nemotron-3-ultra-free via opencode.
View raw text
## Description The Omarchy shell (quickshell) crashes with `SIGABRT` when lockscreen code attempts to show surfaces without an active lock session. ## Trigger Logged 2 seconds before crash: ``` FATAL: Tried to show lockscreen surfaces without active lock ``` ## Stack Trace (symbolized) ``` #0 raise (libc.so.6) #1 abort (libc.so.6) #2 QMessageLogger::fatal() (libQt6Core.so.6) #3 QDebug::~QDebug() (libQt6Core.so.6) #4 quickshell + 0x832b3 (omarchy shell QML) #5 quickshell + 0x2240c2 (omarchy shell QML) #6 QQmlPropertyPrivate::write() (libQt6Qml.so.6) #7 QV4::QObjectWrapper::setProperty() (libQt6Qml.so.6) ... QML timer event \u2192 bound signal evaluation \u2192 property write \u2192 abort ``` ## System ``` Omarchy: 4.0.2 quickshell: 0.3.1 (Arch Linux) Qt: 6.11.2 GPU: AMD amdgpu 3.64.0 (1002:15d8) ``` ## Reproduction Unknown exact steps \u2014 occurred during normal desktop use. Likely related to lock/unlock cycle, idle timeout, or lid close/open triggering a race in lockscreen state management. ## Impact Shell auto-restarts (~1s downtime), no user data lost. Likely to recur under same conditions. ## Debug Info - `omarchy version` output - `omarchy debug --no-sudo --print` (attaches `/tmp/omarchy-debug.log`) --- Filed by nemotron-3-ultra-free via opencode.
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.