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 doesn't have keyboard focus until clicked
Reported by r3d3n0d0 · 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
What happened
After the session locks (idle timeout or manual lock), the password field on
the lock screen does not have keyboard focus. Typing does nothing until I
click into the field first. This happens consistently, every lock/unlock
cycle.
What I expected
The password field should already have keyboard focus when the lock screen
appears, so I can start typing the password immediately without clicking.
Steps to reproduce
- Lock the session (
omarchy system lock, or letidle.locktrigger it). - As soon as the lock screen appears, start typing the password without
clicking anywhere.
3. Nothing is entered into the field. Click into the field, then typing
works.
Likely cause
shell/plugins/lock/LockView.qml already tries to auto-focus the field:
Component.onCompleted: {
syncPasswordText()
if (inputEnabled) Qt.callLater(forcePasswordFocus)
}
onInputEnabledChanged: {
if (inputEnabled) Qt.callLater(forcePasswordFocus)
}inputEnabled is bound to root.lockRequested in Service.qml, which is
set true immediately in beginLock() — at the very start of the lock
sequence, before the Wayland session-lock surface actually has compositor
keyboard focus. Journal output from Service.qml's own event log shows the
gap between the two:
18:37:33.031Z lock-requested
18:37:33.031Z lock-pending: screen-stabilizing
18:37:33.580Z secure=true <- ~550ms laterforcePasswordFocus() fires (via Qt.callLater) right at lock-requested,
well before secure=true — i.e. before WlSessionLock.secure confirms the
compositor has actually granted the surface keyboard focus. The QML-levelforceActiveFocus() call succeeds against the item, but doesn't correspond
to real Wayland keyboard focus yet, so it's a no-op in practice. Clicking
the field afterward re-triggers forcePasswordFocus() via the MouseArea,
which works because by then the surface is actually focused.
A fix would be to move (or also trigger) the auto-focus call offonSecureStateChanged (when secure becomes true) rather than only offinputEnabled, or add a short retry similar to the existingsessionLockStabilizeTimer pattern already used for the analogous "wait for
the compositor to settle" problem elsewhere in Service.qml.
System details
- Omarchy: 4.0.1-1
- Hyprland: 0.56.2
- Quickshell: 0.3.1
- Kernel: 7.1.9-arch1-2
- Session: Wayland, single monitor (eDP-1, scale 1.5)
- GPU: Intel TigerLake-LP Iris Xe (i915) + NVIDIA GTX 1650 Ti Mobile (nvidia) — hybrid graphics laptop
omarchy debug --no-sudo --print is unavailable on this install — there's nodebug subcommand registered despite omarchy --help listing it as a
common command (Unknown Omarchy command: omarchy debug). Diagnostics above
were gathered manually instead.
View raw text
## What happened
After the session locks (idle timeout or manual lock), the password field on
the lock screen does not have keyboard focus. Typing does nothing until I
click into the field first. This happens consistently, every lock/unlock
cycle.
## What I expected
The password field should already have keyboard focus when the lock screen
appears, so I can start typing the password immediately without clicking.
## Steps to reproduce
1. Lock the session (`omarchy system lock`, or let `idle.lock` trigger it).
2. As soon as the lock screen appears, start typing the password without
clicking anywhere.
3. Nothing is entered into the field. Click into the field, then typing
works.
## Likely cause
`shell/plugins/lock/LockView.qml` already tries to auto-focus the field:
```qml
Component.onCompleted: {
syncPasswordText()
if (inputEnabled) Qt.callLater(forcePasswordFocus)
}
onInputEnabledChanged: {
if (inputEnabled) Qt.callLater(forcePasswordFocus)
}
```
`inputEnabled` is bound to `root.lockRequested` in `Service.qml`, which is
set `true` immediately in `beginLock()` — at the very start of the lock
sequence, before the Wayland session-lock surface actually has compositor
keyboard focus. Journal output from `Service.qml`'s own event log shows the
gap between the two:
```
18:37:33.031Z lock-requested
18:37:33.031Z lock-pending: screen-stabilizing
18:37:33.580Z secure=true <- ~550ms later
```
`forcePasswordFocus()` fires (via `Qt.callLater`) right at `lock-requested`,
well before `secure=true` — i.e. before `WlSessionLock.secure` confirms the
compositor has actually granted the surface keyboard focus. The QML-level
`forceActiveFocus()` call succeeds against the item, but doesn't correspond
to real Wayland keyboard focus yet, so it's a no-op in practice. Clicking
the field afterward re-triggers `forcePasswordFocus()` via the `MouseArea`,
which works because by then the surface is actually focused.
A fix would be to move (or also trigger) the auto-focus call off
`onSecureStateChanged` (when `secure` becomes `true`) rather than only off
`inputEnabled`, or add a short retry similar to the existing
`sessionLockStabilizeTimer` pattern already used for the analogous "wait for
the compositor to settle" problem elsewhere in `Service.qml`.
## System details
- Omarchy: 4.0.1-1
- Hyprland: 0.56.2
- Quickshell: 0.3.1
- Kernel: 7.1.9-arch1-2
- Session: Wayland, single monitor (eDP-1, scale 1.5)
- GPU: Intel TigerLake-LP Iris Xe (i915) + NVIDIA GTX 1650 Ti Mobile (nvidia) — hybrid graphics laptop
`omarchy debug --no-sudo --print` is unavailable on this install — there's no
`debug` subcommand registered despite `omarchy --help` listing it as a
common command (`Unknown Omarchy command: omarchy debug`). Diagnostics above
were gathered manually instead.
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/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.