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 race — forcePasswordFocus() fires before WlSessionLock.secure becomes true
Reported by work-aalp · filed Aug 31, 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
System details
NVIDIA 4090, Omarchy Quattro, Apple Magic Keyboard (1st Gen),
13th Gen Intel(R) Core(TM) i9-13900K (16+16) @ 5.80 GHz
GeForce RTX 4090
What's wrong?
Environment: Omarchy 4.0.1-1 (package version; /usr/share/omarchy/version reports 4.0.0.alpha)
Description:
When the lock screen appears, the password field sometimes doesn't receive keyboard input — no keystrokes register — until you click into the field with the mouse first.
Root cause (confirmed via journalctl):
In Service.qml, LockView.inputEnabled is bound to root.lockRequested, and when that becomes true, LockView.qml's onInputEnabledChanged handler calls forcePasswordFocus(). However,
lockRequested becomes true ~500ms before the actual Wayland session lock (WlSessionLock.secure) actually hands keyboard input over to the lock surface:
17:34:31.287Z lock-requested <- forcePasswordFocus() fires here
17:34:31.808Z secure=true <- Wayland ACTUALLY routes keyboard input here
Service.qml's sessionLock.onSecureStateChanged handler only calls root.startFingerprint() — it never re-focuses the password field. As a result, the QML-level focus request happens
before real keyboard input is routed to the surface, so the first keystrokes are lost and the user has to click into the field with the mouse, which triggers forcePasswordFocus()
again via MouseArea.onClicked.
Relevant files:
- shell/plugins/lock/LockView.qml — onInputEnabledChanged: { if (inputEnabled) Qt.callLater(forcePasswordFocus) }
- shell/plugins/lock/Service.qml — sessionLock.onSecureStateChanged (starts fingerprint auth, doesn't refocus the password field)
Suggested fix: Add a call to lockView.forcePasswordFocus() inside onSecureStateChanged (when secure becomes true), so the focus request is repeated at the moment keyboard input
actually arrives.
Steps to reproduce:
1. Lock the screen (manually, or after resuming from suspend).
2. As soon as the lock screen appears, try typing the password immediately.
3. No characters appear; you have to click into the password field with the mouse first.
View raw text
### System details
NVIDIA 4090, Omarchy Quattro, Apple Magic Keyboard (1st Gen),
13th Gen Intel(R) Core(TM) i9-13900K (16+16) @ 5.80 GHz
GeForce RTX 4090
### What's wrong?
Environment: Omarchy 4.0.1-1 (package version; /usr/share/omarchy/version reports 4.0.0.alpha)
Description:
When the lock screen appears, the password field sometimes doesn't receive keyboard input — no keystrokes register — until you click into the field with the mouse first.
Root cause (confirmed via journalctl):
In Service.qml, LockView.inputEnabled is bound to root.lockRequested, and when that becomes true, LockView.qml's onInputEnabledChanged handler calls forcePasswordFocus(). However,
lockRequested becomes true ~500ms before the actual Wayland session lock (WlSessionLock.secure) actually hands keyboard input over to the lock surface:
17:34:31.287Z lock-requested <- forcePasswordFocus() fires here
17:34:31.808Z secure=true <- Wayland ACTUALLY routes keyboard input here
Service.qml's sessionLock.onSecureStateChanged handler only calls root.startFingerprint() — it never re-focuses the password field. As a result, the QML-level focus request happens
before real keyboard input is routed to the surface, so the first keystrokes are lost and the user has to click into the field with the mouse, which triggers forcePasswordFocus()
again via MouseArea.onClicked.
Relevant files:
- shell/plugins/lock/LockView.qml — onInputEnabledChanged: { if (inputEnabled) Qt.callLater(forcePasswordFocus) }
- shell/plugins/lock/Service.qml — sessionLock.onSecureStateChanged (starts fingerprint auth, doesn't refocus the password field)
Suggested fix: Add a call to lockView.forcePasswordFocus() inside onSecureStateChanged (when secure becomes true), so the focus request is repeated at the moment keyboard input
actually arrives.
Steps to reproduce:
1. Lock the screen (manually, or after resuming from suspend).
2. As soon as the lock screen appears, try typing the password immediately.
3. No characters appear; you have to click into the password field with the mouse first.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/9523· 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.