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 loses keyboard focus after suspend/resume, requires mouse click to type password
Reported by kolachaitu · filed Sep 8, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6858 (R-1866). GitHub close reason: completed.
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
What happened
After waking the laptop from suspend, the Omarchy lock screen (Quickshell LockView) is shown and the password field is visible with its cursor blinking, but keyboard input goes nowhere — typing does nothing. Moving the trackpad/mouse and clicking on the password field is required before the keyboard starts working and I can type my password. Only then does it authenticate normally (once focused, everything works fine — this isn't an auth/PAM issue).
What I expected
To be able to type my password immediately after waking from sleep, with no mouse/trackpad interaction needed — same as when locking manually mid-session (that case reportedly does not require a click first).
Steps to reproduce
- Lock the session (or let it idle-lock) so the screen is
secure=true. - Suspend the laptop (lid close or
omarchy system locktimeout → suspend). - Wake the laptop.
- Try to type the password directly — no response.
- Move the mouse/trackpad and click into the password field — typing now works.
Diagnostics
journalctl --user shows the lock stayed in the same secured session across the suspend/resume cycle — there's no new lock-requested/secure=true pair after resume, only the eventual unlocked once I clicked and typed:
Sep 07 13:15:48 lock-requested
Sep 07 13:15:48 lock-pending: screen-stabilizing
Sep 07 13:15:48 secure=true <- locked before suspend
--- suspend 13:15:49, resume 22:54:24 (kernel: PM: suspend exit) ---
Sep 07 23:01:47 secure=false <- only happens once I click + type (7 min after resume, once I got to the laptop)
Sep 07 23:01:47 unlockedSo the lock surface/session isn't being recreated on resume — this points at Hyprland not restoring/handing back Wayland keyboard focus to the existing ext-session-lock surface after the suspend/resume cycle, even though input:follow_mouse = 1 and misc:allow_session_lock_restore = true are both at Omarchy's shipped defaults.
omarchy version: 4.0.2-1- Hyprland: 0.56.2 (commit efb509937)
- Kernel: 7.1.9-arch1-2
- GPU: hybrid Intel UHD 620 (i915) + NVIDIA MX150 (nvidia-580xx-utils 580.178.04, RTD3 disabled)
- Laptop: Razer Blade Stealth (RZ09-02812E71)
Related upstream reports that look like the same class of bug (none confirmed-fixed as of filing):
- hyprwm/Hyprland#3581 — swaylock/waylock lose focus after resume
- hyprwm/Hyprland#5884 — keyboard focus does not work with mouse click right after unlock
- basecamp/omarchy#2991 — Can not interact with lock screen after opening lid
- basecamp/omarchy#3724 — Login screen freezes when waking up after suspend
View raw text
### What happened After waking the laptop from suspend, the Omarchy lock screen (Quickshell `LockView`) is shown and the password field is visible with its cursor blinking, but keyboard input goes nowhere — typing does nothing. Moving the trackpad/mouse and clicking on the password field is required before the keyboard starts working and I can type my password. Only then does it authenticate normally (once focused, everything works fine — this isn't an auth/PAM issue). ### What I expected To be able to type my password immediately after waking from sleep, with no mouse/trackpad interaction needed — same as when locking manually mid-session (that case reportedly does not require a click first). ### Steps to reproduce 1. Lock the session (or let it idle-lock) so the screen is `secure=true`. 2. Suspend the laptop (lid close or `omarchy system lock` timeout → suspend). 3. Wake the laptop. 4. Try to type the password directly — no response. 5. Move the mouse/trackpad and click into the password field — typing now works. ### Diagnostics `journalctl --user` shows the lock stayed in the *same* secured session across the suspend/resume cycle — there's no new `lock-requested`/`secure=true` pair after resume, only the eventual `unlocked` once I clicked and typed: ``` Sep 07 13:15:48 lock-requested Sep 07 13:15:48 lock-pending: screen-stabilizing Sep 07 13:15:48 secure=true <- locked before suspend --- suspend 13:15:49, resume 22:54:24 (kernel: PM: suspend exit) --- Sep 07 23:01:47 secure=false <- only happens once I click + type (7 min after resume, once I got to the laptop) Sep 07 23:01:47 unlocked ``` So the lock surface/session isn't being recreated on resume — this points at Hyprland not restoring/handing back Wayland keyboard focus to the existing `ext-session-lock` surface after the suspend/resume cycle, even though `input:follow_mouse = 1` and `misc:allow_session_lock_restore = true` are both at Omarchy's shipped defaults. - `omarchy version`: 4.0.2-1 - Hyprland: 0.56.2 (commit efb509937) - Kernel: 7.1.9-arch1-2 - GPU: hybrid Intel UHD 620 (i915) + NVIDIA MX150 (nvidia-580xx-utils 580.178.04, RTD3 disabled) - Laptop: Razer Blade Stealth (RZ09-02812E71) Related upstream reports that look like the same class of bug (none confirmed-fixed as of filing): - hyprwm/Hyprland#3581 — swaylock/waylock lose focus after resume - hyprwm/Hyprland#5884 — keyboard focus does not work with mouse click right after unlock - basecamp/omarchy#2991 — Can not interact with lock screen after opening lid - basecamp/omarchy#3724 — Login screen freezes when waking up after suspend
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
- Related PRpr/13907· confirmed
- Related PRpr/8560· confirmed
- Fixed bypr/7471· 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.