Proof Portal

Sign in
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-4695GitHub issuePublicFixed

Lock screen loses keyboard focus after lid open (resume); requires a mouse click to type

Reported by andersmar · filed Aug 26, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6858 (R-1866). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked 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?
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

Lock screen loses keyboard focus after lid open (resume); requires a mouse click to typerevision 1 · captured 2026-10-04 12:03 UTC via poll

Description

After the laptop lid is opened (screen was locked at lid close, then the machine suspended), the lock screen's password field does not have keyboard focus. Typing does nothing until the mouse is clicked once inside the lock screen. Moving the mouse without clicking does not restore focus either.

Steps to reproduce

  1. Close the laptop lid (this locks the screen and the machine suspends).
  2. Wait, then open the lid.
  3. Without touching the mouse, try typing the password — nothing appears in the field.
  4. Click anywhere on the lock screen, then type — now it works.

Expected behavior

The password field should already have keyboard focus (or regain it automatically on wake) after opening the lid, without requiring a mouse click.

Root cause (found while investigating)

In /usr/share/omarchy/shell/plugins/lock/LockView.qml, keyboard focus on passwordInput is only requested in two places:

  • Component.onCompleted — fires once, when the lock QML item is first created (at lid-close time, before suspend).
  • MouseArea.onClicked — explicitly calls root.forcePasswordFocus().

MouseArea.onPositionChanged (mouse move) and Keys.onPressed only emit wakeRequested(), which in Service.qml's runWake() just runs omarchy-system-wake (turns the display back on) — it never calls forcePasswordFocus(). Hyprland appears to drop keyboard focus on the lock's layer-shell surface across the suspend/resume cycle, and nothing re-requests it afterward except an explicit click.

Workaround

Cloned the plugin (omarchy plugin clone omarchy.lock) and added a root.forcePasswordFocus() call to MouseArea.onPositionChanged alongside the existing onClicked handler, so any mouse movement after wake also re-asserts focus. Confirms the diagnosis — with that change, moving the mouse (no click needed) restores typing.

System

  • Omarchy: 4.0.1-1
  • Kernel: 7.1.9-arch1-2
  • CPU: Intel(R) Core(TM) Ultra 9 185H
  • GPU: Intel Meteor Lake-P (Arc Graphics) + NVIDIA GeForce RTX 4060 Max-Q (hybrid graphics)
  • Machine: Lenovo 83DN
  • omarchy debug --no-sudo --print is not a recognized command in this version (omarchy commands --all has no debug entry), so no diagnostic log is attached.
View raw text
## Description

After the laptop lid is opened (screen was locked at lid close, then the machine suspended), the lock screen's password field does not have keyboard focus. Typing does nothing until the mouse is clicked once inside the lock screen. Moving the mouse without clicking does not restore focus either.

## Steps to reproduce

1. Close the laptop lid (this locks the screen and the machine suspends).
2. Wait, then open the lid.
3. Without touching the mouse, try typing the password — nothing appears in the field.
4. Click anywhere on the lock screen, then type — now it works.

## Expected behavior

The password field should already have keyboard focus (or regain it automatically on wake) after opening the lid, without requiring a mouse click.

## Root cause (found while investigating)

In `/usr/share/omarchy/shell/plugins/lock/LockView.qml`, keyboard focus on `passwordInput` is only requested in two places:

- `Component.onCompleted` — fires once, when the lock QML item is first created (at lid-close time, before suspend).
- `MouseArea.onClicked` — explicitly calls `root.forcePasswordFocus()`.

`MouseArea.onPositionChanged` (mouse move) and `Keys.onPressed` only emit `wakeRequested()`, which in `Service.qml`'s `runWake()` just runs `omarchy-system-wake` (turns the display back on) — it never calls `forcePasswordFocus()`. Hyprland appears to drop keyboard focus on the lock's layer-shell surface across the suspend/resume cycle, and nothing re-requests it afterward except an explicit click.

## Workaround

Cloned the plugin (`omarchy plugin clone omarchy.lock`) and added a `root.forcePasswordFocus()` call to `MouseArea.onPositionChanged` alongside the existing `onClicked` handler, so any mouse movement after wake also re-asserts focus. Confirms the diagnosis — with that change, moving the mouse (no click needed) restores typing.

## System

- Omarchy: 4.0.1-1
- Kernel: 7.1.9-arch1-2
- CPU: Intel(R) Core(TM) Ultra 9 185H
- GPU: Intel Meteor Lake-P (Arc Graphics) + NVIDIA GeForce RTX 4060 Max-Q (hybrid graphics)
- Machine: Lenovo 83DN
- `omarchy debug --no-sudo --print` is not a recognized command in this version (`omarchy commands --all` has no `debug` entry), so no diagnostic log is attached.

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

No decision has been recorded yet.