Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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.
Compositor-side lock loss with a request outstanding is treated as a finished unlock; no re-lock
Medium-severity issue, currently open.
Description
The issue as recorded.
WlSessionLock.onLockStateChanged (shell/plugins/lock/Service.qml:339-345): when locked flips false while lockRequested still holds, the branch clears lockRequested and pendingSessionLock, resets auth state and calls runWake() with no queueSessionLock/beginLock. That locked flip is an ext-session-lock finish/acquire failure delivered by the compositor rather than finishUnlock. finishUnlock sets lockRequested=false BEFORE locked=false, so this branch only runs for an external drop. A spontaneous protocol-level unlock then fails open (session visible, no re-lock attempted), unlike the no-real-screen path which keeps retrying.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
./pocs/lock-service-failopen-runtime.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
./pocs/lock-service-failopen-runtime.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
rare in practice: requires a compositor-side lock drop while the shell still holds the request
The fix
Re-queue the lock (queueSessionLock) when locked flips false while lockRequested is outstanding, instead of treating it as an unlock
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
Touch this finding and you re-check 6 requirements · 3 code files · 5 tests.
- omarchy-system-lock
- LockView.qml
- Service.qml
- system-lock-test.sh
- lock-fingerprint-indicator-test.sh
- lock-missing-pam-test.sh
- lock-blank-fingerprint-test.sh
- lock-password-overflow-test.sh
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Per-requirement evidence
For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-lock-spontaneous-unlock-fail-open.yaml
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.