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.
Lock screen delayed after waking up from suspend
Reported by remshams · filed Aug 24, 2025Closed upstream on 2025-08-24 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
On one of my installations, the lock screen only shows up a few seconds after waking up from sleep. Until then, the content of the currently active workspace is visible.
It looks like, depending on the performance of the CPU and/or SSD, the before_sleep_cmd (as defined in the hypridle.conf) does not have enough time to execute before the system goes to sleep and only completes after the computer wakes up from suspend.
I was able to work around the issue (though I don't like it) by executing loginctl lock-session && sleep 1 && systemctl suspend instead of the omarchy suspend command (from the menu). So it looks like it's a timing-related issue.
I saw the issue mentioned a few times on Discord and was wondering if it's a more widespread issue.
View raw text
On one of my installations, the lock screen only shows up a few seconds after waking up from sleep. Until then, the content of the currently active workspace is visible. It looks like, depending on the performance of the CPU and/or SSD, the `before_sleep_cmd` (as defined in the `hypridle.conf`) does not have enough time to execute before the system goes to sleep and only completes after the computer wakes up from suspend. I was able to work around the issue (though I don't like it) by executing `loginctl lock-session && sleep 1 && systemctl suspend` instead of the omarchy suspend command (from the menu). So it looks like it's a timing-related issue. I saw the issue mentioned a few times on Discord and was wondering if it's a more widespread issue.
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.