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.
[Bug] `omarchy-system-sleep-lock` hangs for 12000ms on suspend due to stuck `lock-pending: screen-stabilizing` state
Reported by OliverZhangBuild · filed Oct 11, 2026 · open at source
R-942 is the earliest report of this defect — filed Sep 5, 2026, open upstream. This report (filed Oct 11, 2026) describes the same defect, so it is folded under it in the inbox.
Decided by agents · verified· Oct 11, 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
OS: Omarchy 4 | Compositor: Hyprland
What's wrong?
When initiating a suspend/hibernate (e.g. by pressing the physical power button or closing the lid), the display takes 12 full seconds (~12000ms) to blank and sleep. After waking, a critical desktop notification is displayed:
> Screen did not lock before suspend
> The session was left unlocked (the shell did not secure the session within 12000ms).
Manual lock via omarchy system lock appears to trigger immediately, but omarchy-system-sleep-lock consistently exhausts its entire budget_cap_ms=12000 window before falling back.
Steps to Reproduce
- Start an unlocked graphical session on Omarchy.
- Check lock status:
omarchy-shell lock statusreports clean state. - Lock the screen with
omarchy system lockor Super+Ctrl+L, then unlock via password/fingerprint. - Press the hardware Power button or trigger
systemctl suspend. - Observe: System does not suspend immediately; it hangs for ~12 seconds before the display finally sleeps.
- Upon resume, the notification "Screen did not lock before suspend (the shell did not secure the session within 12000ms)" appears.
Root Cause Analysis & Diagnostic Data
- Stuck `screen-stabilizing` state in `omarchy-shell`:
Inspecting omarchy-shell lock status after unlocking reveals the lock service remains permanently desynced:
{
"locked": true,
"requested": true,
"pending": true,
"sessionLocked": false,
"secure": false,
"realScreens": 1,
"passwordPam": true,
"fingerprint": true,
"fingerprintUnavailable": false,
"authenticating": false,
"lastEvent": "lock-pending: screen-stabilizing",
"lastEventAt": "2026-10-11T03:15:09.446Z"View raw text
### System details
OS: Omarchy 4 | Compositor: Hyprland
### What's wrong?
When initiating a suspend/hibernate (e.g. by pressing the physical power button or closing the lid), the display takes 12 full seconds (~12000ms) to blank and sleep. After waking, a critical desktop notification is displayed:
> **Screen did not lock before suspend**
> *The session was left unlocked (the shell did not secure the session within 12000ms).*
Manual lock via `omarchy system lock` appears to trigger immediately, but `omarchy-system-sleep-lock` consistently exhausts its entire `budget_cap_ms=12000` window before falling back.
---
### Steps to Reproduce
1. Start an unlocked graphical session on Omarchy.
2. Check lock status: `omarchy-shell lock status` reports clean state.
3. Lock the screen with `omarchy system lock` or Super+Ctrl+L, then unlock via password/fingerprint.
4. Press the hardware Power button or trigger `systemctl suspend`.
5. Observe: System does not suspend immediately; it hangs for ~12 seconds before the display finally sleeps.
6. Upon resume, the notification "Screen did not lock before suspend (the shell did not secure the session within 12000ms)" appears.
---
### Root Cause Analysis & Diagnostic Data
1. **Stuck `screen-stabilizing` state in `omarchy-shell`:**
Inspecting `omarchy-shell lock status` after unlocking reveals the lock service remains permanently desynced:
```json
{
"locked": true,
"requested": true,
"pending": true,
"sessionLocked": false,
"secure": false,
"realScreens": 1,
"passwordPam": true,
"fingerprint": true,
"fingerprintUnavailable": false,
"authenticating": false,
"lastEvent": "lock-pending: screen-stabilizing",
"lastEventAt": "2026-10-11T03:15:09.446Z"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-942Stalled lock latches lockRequested, so every later lock() returns "ok" without locking — machine suspends unlocked· 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.