Proof Portal

Omarchy

ProbeLabs65 findings · 95 requirements

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.

Inbox

ReportR-156GitHub issuePublicFixed

Lock screen re-blanks a slow-waking external monitor before it shows a picture (5 s blank timer), so wake needs several tries

Reported by nearcritical · filed Sep 23, 2026Closed upstream on 2026-10-08 by its own reporter nearcritical, as a duplicate of #8847 (R-1289). GitHub close reason: duplicate.

Open at source

Received and recorded verbatim. Nothing has been checked yet.

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

Lock screen re-blanks a slow-waking external monitor before it shows a picture (5 s blank timer), so wake needs several triesrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Omarchy 4.0.4-1, Hyprland 0.56.2-2, Quickshell 0.3.1-1. AMD Radeon 680M (Rembrandt). Dell U2725QE at 3840x2160@120 over DisplayPort; the same happened earlier over USB-C (DP Alt Mode).

What's wrong?

After the idle lock has blanked the display, a key press wakes it, but the monitor only shows "no DisplayPort signal", or shows the lock screen for a moment, and then goes dark again. It usually takes several key presses to get a picture that stays. Every one of those key presses is typed into the password field, so the first unlock attempt fails unless the field is cleared with Escape first.

Expected: One key press wakes the monitor and the lock screen stays visible long enough to type the password.

Evidence: The Hyprland log for a single wake shows the output being switched off and on three times in a row:

drm: Disabling output DP-2
drm: Connector DP-2 enabledState changed true -> false
drm: Modesetting DP-2 with [email protected]
drm: Connector DP-2 enabledState changed false -> true
drm: Disabling output DP-2
drm: Connector DP-2 enabledState changed true -> false
drm: Modesetting DP-2 with [email protected]
drm: Connector DP-2 enabledState changed false -> true
drm: Disabling output DP-2
drm: Connector DP-2 enabledState changed true -> false
drm: Modesetting DP-2 with [email protected]
drm: Connector DP-2 enabledState changed false -> true

The machine did not suspend (no suspend or resume in the journal); this is the lock screen's own blank. There was no hotplug or disconnect during these cycles.

Cause (as far as I can tell): plugins/lock/Service.qml arms idleBlankTimer (5000 ms) on every key press or mouse move, and when it fire-display off`. The timer starts whenthe key is pressed, not when the monitor is actually showing a picture. This monitor seems to take
roughly that long to come out of stan about 5 s against about 1 s on anolder UltraSharp), so the blank lands before or just as the picture appears.

Comparison: A Windows laptop on the same monitor wakes it from sleep reliably, every time.

Workaround: Press Escape (which wakes the display and clears the field), then type the password and
press Enter blind. Each key press ress.

Possible fixes: A longer blank deuggests (30–60 s), or starting thecountdown only once the output has actually come back. A configurable delay would also cover it.

Related: #11411, #11066, #11072 (draft idle.blankDisplay opt-out), #12327.

View raw text

### System details

Omarchy 4.0.4-1, Hyprland 0.56.2-2, Quickshell 0.3.1-1. AMD Radeon 680M (Rembrandt). Dell U2725QE at 3840x2160@120 over DisplayPort; the same happened earlier over USB-C (DP Alt Mode).

### What's wrong?

**Expected:** One key press wakes the monitor and the lock screen stays visible long enough to type the password.

**Evidence:** The Hyprland log for a single wake shows the output being switched off and on three times in a row:

The machine did not suspend (no suspend or resume in the journal); this is the lock screen's own blank. There was no hotplug or disconnect during these cycles.

**Cause (as far as I can tell):** `plugins/lock/Service.qml` arms `idleBlankTimer` (5000 ms) on every key press or mouse move, and when it fire-display off`. The timer starts whenthe key is pressed, not when the monitor is actually showing a picture. This monitor seems to take
roughly that long to come out of stan about 5 s against about 1 s on anolder UltraSharp), so the blank lands before or just as the picture appears.

**Comparison:** A Windows laptop on the same monitor wakes it from sleep reliably, every time.

**Workaround:** Press Escape (which wakes the display and clears the field), then type the password and
press Enter blind. Each key press ress.

**Possible fixes:** A longer blank deuggests (30–60 s), or starting thecountdown only once the output has actually come back. A configurable delay would also cover it.

**Related:** #11411, #11066, #11072 (draft `idle.blankDisplay` opt-out), #12327.

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

Fixed bypr/8773· confirmed
Fixed bypr/8561· confirmed

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.

Proof

History & reports

Reference