Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1866GitHub issuePublicFixed

Lock screen auto-focus not working

Reported by Obamium3157 · filed Aug 14, 2026 · open at source

In the audited area (lock) — decided by agents · verified. Not validated yet.

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?
AreaIn the audited arealock· Decided by agents · verified
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. So far: not a duplicate of another report — decided by agents · verified; in the audited area (lock) — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Lock screen auto-focus not workingrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy: 4.0.0.r1732.g864b0d0-1 (edge channel). Kernel: 7.1.8-arch1-3; Hyprland: 0.56.2-1; quickshell-git: 0.3.0.r20.g28771c7-1. CPU: 11th Gen Intel Core i5-1135G7; GPU: Intel Iris Xe + NVIDIA RTX 3050 Mobile

What's wrong?

The Quickshell lock screen (omarchy.lock service, shell/plugins/lock/LockView.qml) does not auto-focus the password field. After locking, the user must click the field before typing works.

Root cause

LockView.qml:55-77 calls passwordInput.forceActiveFocus() once from Component.onCompleted and once from onInputEnabledChanged, both via Qt.callLater. The WlSessionLockSurface/LockView is created ~500 ms before Hyprland maps the surface and hands over keyboard focus. So forceActiveFocus() lands while the lock window is still hidden/inactive, and the window's later activation does not re-apply the pending active focus. Clicking works because it sets focus while the window is already active.

Proposed fix (verified on my machine)

Retry forceActiveFocus() until the field actually holds focus, re-armed at lock-request and when auth finishes:

function armFocusRetry() {
    if (!inputEnabled) return
    focusRetry.remaining = 50
    focusRetry.restart()
}
onInputEnabledChanged: {
    if (inputEnabled) { Qt.callLater(forcePasswordFocus); armFocusRetry() }
}
onAuthenticatingPasswordChanged: {
    if (!authenticatingPassword && inputEnabled) armFocusRetry()
}
Component.onCompleted: {
    syncPasswordText()
    if (inputEnabled) { Qt.callLater(forcePasswordFocus); armFocusRetry() }
}
Timer {
    id: focusRetry
    interval: 120
    repeat: true
    property int remaining: 0
    onTriggered: {
        if (!root.inputEnabled || root.authenticatingPassword || passwordInput.activeFocus) { stop(); return }
        root.forcePasswordFocus()
        remaining -= 1
        if (remaining <= 0) stop()
    }
}
View raw text
### System details

Omarchy: 4.0.0.r1732.g864b0d0-1 (edge channel). Kernel: 7.1.8-arch1-3; Hyprland: 0.56.2-1; quickshell-git: 0.3.0.r20.g28771c7-1. CPU: 11th Gen Intel Core i5-1135G7; GPU: Intel Iris Xe + NVIDIA RTX 3050 Mobile

### What's wrong?

The Quickshell lock screen (`omarchy.lock` service, `shell/plugins/lock/LockView.qml`) does not auto-focus the password field. After locking, the user must click the field before typing works.

## Root cause
`LockView.qml:55-77` calls `passwordInput.forceActiveFocus()` once from `Component.onCompleted` and once from `onInputEnabledChanged`, both via `Qt.callLater`. The `WlSessionLockSurface/LockView` is created ~500 ms before Hyprland maps the surface and hands over keyboard focus. So `forceActiveFocus()` lands while the lock window is still hidden/inactive, and the window's later activation does not re-apply the pending active focus. Clicking works because it sets focus while the window is already active.

## Proposed fix (verified on my machine)
Retry `forceActiveFocus()` until the field actually holds focus, re-armed at lock-request and when auth finishes:
```qml
function armFocusRetry() {
    if (!inputEnabled) return
    focusRetry.remaining = 50
    focusRetry.restart()
}
onInputEnabledChanged: {
    if (inputEnabled) { Qt.callLater(forcePasswordFocus); armFocusRetry() }
}
onAuthenticatingPasswordChanged: {
    if (!authenticatingPassword && inputEnabled) armFocusRetry()
}
Component.onCompleted: {
    syncPasswordText()
    if (inputEnabled) { Qt.callLater(forcePasswordFocus); armFocusRetry() }
}
Timer {
    id: focusRetry
    interval: 120
    repeat: true
    property int remaining: 0
    onTriggered: {
        if (!root.inputEnabled || root.authenticatingPassword || passwordInput.activeFocus) { stop(); return }
        root.forcePasswordFocus()
        remaining -= 1
        if (remaining <= 0) stop()
    }
}
```

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
  • Related PRpr/9523· confirmed
  • Fixed bypr/7164· confirmed
  • Related PRpr/10944· confirmed
  • Fixed bypr/7471· confirmed
  • Related PRpr/8560· confirmed
  • Fixed bypr/8930· 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.

  • Decided by agents · verified: not a duplicate of another report
  • Decided by agents · verified: in the audited area (lock)

The outcome (valid, duplicate, not a bug, …) is not decided yet.