Proof Portal

Sign in
Project overview

Omarchy

ProbeLabsviewing a historical run

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.

Viewing historical run b16f5e6Oct 2, 2026, 01:38 AMpr/10631Back to current
Back to findings
Known issueKI-LOCK-SCREENS-CHANGE-BLANK-LOST

Screen add/remove while locked clears the blank intent and never re-arms the idle blank timer

OpenReviewedLow

Low-severity issue, currently open.

Description

The issue as recorded.

onScreensChanged (shell/plugins/lock/Service.qml:666-674) sets displaysBlank = false (so a returning panel shows the wallpaper) but calls neither armBlankTimer nor runWake. After the one-shot idleBlankTimer has fired, nothing restarts the 5s countdown, and a newly added output falls back to displaysBlank in the DPMS map. So after any hotplug/unplug while locked, all displays stay awake until the next keypress re-runs the idle path.

Affected requirements

The requirement(s) this issue violates — click through to the spec.

SW-REQ-260912-ND55

Severity, explained

Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).

LowRated severity — the impact if this issue is exploited or hit.
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.

Known issue reproducedprofileknown_issue_reproducerprovesSW-REQ-260912-ND55
Reproducer test
Run it yourself
./pocs/crs-260930-ttvk-qml-static.sh
Covers (2)
Last run Sep 30, 2026, 11:02 PM

Reproduction steps

Technical steps for your engineers to confirm the issue by hand.

./pocs/crs-260930-ttvk-qml-static.sh

What protects you, and the fix

What limits your exposure today, and the planned remediation.

What protects you now

any keypress restarts the cycle

The fix

After clearing displaysBlank in onScreensChanged, re-arm the idle blank timer (or runWake-then-arm) so the power path resumes

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.

Tracing blast radius…

Touch this finding and you re-check 1 requirements · 2 code files · 1 tests.

Requirements (1)
SW-REQ-260912-ND55
Code files (2)
  • LockView.qml
  • Service.qml
Tests (1)
  • lock-blank-fingerprint-test.sh

Per-requirement evidence

For each requirement this finding touches: the implementing code, verifying tests, and proof obligations that discharge it.

SW-REQ-260912-ND55
Implementing code (3)
  • shell/plugins/lock/LockView.qml
  • shell/plugins/lock/LockView.qml
    submitted
  • shell/plugins/lock/Service.qml
Tests & evidence (1)
  • test/shell.d/lock-blank-fingerprint-test.sh

Evidence trail

The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.

  • proof/evidence/ki-lock-screens-change-blank-lost.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.

Sign in to discuss this with the proof team.Sign in