OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend low common DISPUTE

Work around the Omarchy lock screen not accepting keystrokes after lid-open

omarchyhyprlandwaylandlaptopnvidiaintel
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The issue is real and the root-cause analysis is accurate. basecamp/omarchy#8520 describes the password field lacking keyboard focus after resume but not on manual lock, on Omarchy 4.0.1-1 with hybrid Intel+NVIDIA, and attributes it to forceActiveFocus() firing before "the WlSessionLock surface has actually been mapped and granted exclusive keyboard focus by the compositor". The workarounds (click the field, widen the after_sleep_cmd delay) are sound and the config block matches upstream apart from the intended sleep 2. The defect is the diagnostic step: there is no omarchy-sleep-lock.service in the Omarchy repository. Omarchy handles pre-sleep locking via hypridle's inhibit_sleep = 3 and hooks under default/systemd/system-sleep/. Those two commands will just report that the unit could not be found, sending the user chasing a non-existent service.

The cause above was rewritten on 2026-08-30 to match this note; the fix was corrected by the audit itself.

Symptom

I open the lid, the lock screen is there, I type my password and nothing appears in the field. I have to click the password box first, then it works. Locking manually while awake is fine. Only resume is affected.

Cause

A timing race: the password field calls forceActiveFocus() as soon as the lock is *requested*, not once the WlSessionLock surface has actually been mapped and granted exclusive keyboard focus by the compositor. On resume the lock is set up during the unstable early-resume window, so the focus call lands before the surface exists. Hybrid Intel+NVIDIA laptops make the window wider. Omarchy has no omarchy-sleep-lock.service. Pre-sleep locking is driven by hypridle's inhibit_sleep = 3 together with the hooks under default/systemd/system-sleep/.

Fix

No upstream fix yet. Immediate workaround: click the password field (or press Escape then Tab) before typing.

Widen the post-resume settling window by increasing the delay in after_sleep_cmd:


# ~/.config/hypr/hypridle.conf
general {
    lock_cmd = omarchy-system-lock
    before_sleep_cmd = OMARCHY_LOCK_ONLY=true omarchy-system-lock
    after_sleep_cmd = sleep 2 && omarchy-system-wake
    inhibit_sleep = 3
}

systemctl --user restart hypridle.service 2>/dev/null || { pkill hypridle; uwsm app -- hypridle & }

Replace the omarchy-sleep-lock.service checks. That unit does not exist. Omarchy locks before sleep through hypridle's inhibit_sleep = 3 (lock notify) and systemd sleep hooks, so look there instead:


journalctl -b --since '-1h' | grep -i 'hypridle\|hyprlock\|omarchy-system-lock'
systemd-inhibit --list --what=sleep      # hypridle should hold a sleep inhibitor
ls /usr/lib/systemd/system-sleep/ /etc/systemd/system-sleep/

If hypridle is not holding a sleep inhibitor, inhibit_sleep is not in effect and the machine can suspend before the lock surface is up, which makes the focus race much worse. Confirm hypridle is actually running (pidof hypridle) before tuning delays.

Verify

Suspend, resume, and type immediately. Characters appear in the field without clicking it first.

Sources

omarchy-lockscreen-no-keyboard-focus-after-resume