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.
hyprlock crash while idle — "lockscreen app died" screen on Framework 13
Reported by newtriks · filed May 1, 2026Closed upstream on 2026-07-18 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
System details
Omarchy 3.6.0 - AMD Ryzen™ AI 300 Series - Ryzen™ AI 9 HX 370
What's wrong?
While the laptop was left open and idle, hyprlock launched as expected but then crashed. Hyprland displayed the “Oopsie daisy, it looks like you locked your screen but the lockscreen app died” recovery screen. The system was stuck and required switching to another TTY to recover.
Steps to reproduce:
- Leave the laptop open and idle
- Hyprlock triggers automatically via hypridle
- Screen shows the Hyprland lockscreen crash recovery screen
Recovery steps that work:
ctrl+alt+F3
# log in, then:
hyprctl --instance 0 'keyword misc:allow_session_lock_restore 1'
hyprctl --instance 0 'dispatch exec hyprlock'View raw text
### System details Omarchy 3.6.0 - AMD Ryzen™ AI 300 Series - Ryzen™ AI 9 HX 370 ### What's wrong? While the laptop was left open and idle, hyprlock launched as expected but then crashed. Hyprland displayed the “Oopsie daisy, it looks like you locked your screen but the lockscreen app died” recovery screen. The system was stuck and required switching to another TTY to recover. Steps to reproduce: 1. Leave the laptop open and idle 2. Hyprlock triggers automatically via hypridle 3. Screen shows the Hyprland lockscreen crash recovery screen Recovery steps that work: ``` ctrl+alt+F3 # log in, then: hyprctl --instance 0 'keyword misc:allow_session_lock_restore 1' hyprctl --instance 0 'dispatch exec hyprlock' ```
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.