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 password field loses keyboard focus after resume; only a mouse click restores it
Reported by Adam-Ben-Shoham · filed Sep 6, 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 happens
After the laptop suspends and I wake it, the lock screen comes back with the password field visible, but it does not have keyboard focus. Typing does nothing — no dots appear, no keystroke registers. The only way to get input working is to click the password field with the mouse or touchpad, after which typing works normally.
It happens on every resume, not intermittently.
What I expected
The password field to hold keyboard focus whenever the lock screen is showing, so that any key press goes straight into it.
Cause (from reading the plugin)
In shell/plugins/lock/LockView.qml, forcePasswordFocus() has only three callers:
Component.onCompleted— fires when the lock surface is first createdonInputEnabledChanged— fires wheninputEnabledflips to trueMouseArea.onClicked— the click that works around this
inputEnabled is bound to root.lockRequested in Service.qml, which stays true for the whole lock, so it does not change across a suspend/resume. If the WlSessionLockSurface loses keyboard focus while it is remapped on resume, nothing takes it back, and the click handler is the only remaining path — which matches the observed behaviour exactly.
Suggested fix
A self-disarming focus guard in LockView.qml restores it. The binding stops the timer as soon as focus returns, so it only runs while focus is actually missing:
Timer {
interval: 200
repeat: true
running: root.inputEnabled && !passwordInput.activeFocus
onTriggered: root.forcePasswordFocus()
}I tested this locally by cloning the plugin with omarchy plugin clone omarchy.lock and patching the clone. It fixes the symptom. I reverted the clone afterwards rather than carry a fork of the lock screen, so I would rather see the fix land upstream than keep it locally.
Steps to reproduce
- Lock the screen, or let the idle lock fire (
idle.lockis 300 in myshell.json). - Let the machine suspend.
- Press a key to wake it.
- Type the password without touching the mouse or touchpad — nothing is entered.
- Click the password field, type again — works.
System
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- quickshell 0.3.1-1
- Kernel 7.1.9-arch1-2
- Dell Inspiron 16 Plus 7620, single internal display (eDP-1)
- Intel Iris Xe + NVIDIA GA107M (GeForce RTX 3050 Ti Mobile)
View raw text
### What happens
After the laptop suspends and I wake it, the lock screen comes back with the password field visible, but it does not have keyboard focus. Typing does nothing — no dots appear, no keystroke registers. The only way to get input working is to click the password field with the mouse or touchpad, after which typing works normally.
It happens on every resume, not intermittently.
### What I expected
The password field to hold keyboard focus whenever the lock screen is showing, so that any key press goes straight into it.
### Cause (from reading the plugin)
In `shell/plugins/lock/LockView.qml`, `forcePasswordFocus()` has only three callers:
- `Component.onCompleted` — fires when the lock surface is first created
- `onInputEnabledChanged` — fires when `inputEnabled` flips to true
- `MouseArea.onClicked` — the click that works around this
`inputEnabled` is bound to `root.lockRequested` in `Service.qml`, which stays true for the whole lock, so it does not change across a suspend/resume. If the `WlSessionLockSurface` loses keyboard focus while it is remapped on resume, nothing takes it back, and the click handler is the only remaining path — which matches the observed behaviour exactly.
### Suggested fix
A self-disarming focus guard in `LockView.qml` restores it. The binding stops the timer as soon as focus returns, so it only runs while focus is actually missing:
```qml
Timer {
interval: 200
repeat: true
running: root.inputEnabled && !passwordInput.activeFocus
onTriggered: root.forcePasswordFocus()
}
```
I tested this locally by cloning the plugin with `omarchy plugin clone omarchy.lock` and patching the clone. It fixes the symptom. I reverted the clone afterwards rather than carry a fork of the lock screen, so I would rather see the fix land upstream than keep it locally.
### Steps to reproduce
1. Lock the screen, or let the idle lock fire (`idle.lock` is 300 in my `shell.json`).
2. Let the machine suspend.
3. Press a key to wake it.
4. Type the password without touching the mouse or touchpad — nothing is entered.
5. Click the password field, type again — works.
### System
- Omarchy 4.0.2-1
- Hyprland 0.56.2
- quickshell 0.3.1-1
- Kernel 7.1.9-arch1-2
- Dell Inspiron 16 Plus 7620, single internal display (eDP-1)
- Intel Iris Xe + NVIDIA GA107M (GeForce RTX 3050 Ti Mobile)
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
- Fixed bypr/13907· confirmed
- Fixed bypr/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.