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.
Numlock not working as expected
Reported by granite4lyfe · filed Aug 25, 2026Closed upstream on 2026-08-25 by its own reporter granite4lyfe, as a duplicate of #7162 (R-1755). 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
AMD 7600X, AMD 9070 XT, Omarchy 4.0.0
What's wrong?
Running Omarchy ISO 4.0.0 on PC, Hyprland 0.56.2, with a Cherry wireless keyboard (which registers as two separate device entries) plus a gaming mouse that also exposes its own "keyboard" HID interface for macro/DPI buttons. Numlock desyncs during live sessions — the LED stays lit, but numeric input stops working until the key is physically cycled — most reliably triggered by a polkit password dialog (easy to reproduce with pkexec true). Confirmed this isn't fixable via config: numlock_by_default only seeds a device's state at connect/session-start, and reissuing it live (hyprctl eval 'hl.config({input={numlock_by_default=true}})') does nothing once devices are already desynced — the actual lock state lives in Hyprland's internal per-device xkb objects, invisible to any hyprctl command. Matches several already-closed-as-"not planned" upstream issues (#9575, #6886, #8288), so this looks like a known architectural limitation around multi-device keyboard state tracking rather than something Omarchy's config can work around.
View raw text
### System details
AMD 7600X, AMD 9070 XT, Omarchy 4.0.0
### What's wrong?
Running Omarchy ISO 4.0.0 on PC, Hyprland 0.56.2, with a Cherry wireless keyboard (which registers as two separate device entries) plus a gaming mouse that also exposes its own "keyboard" HID interface for macro/DPI buttons. Numlock desyncs during live sessions — the LED stays lit, but numeric input stops working until the key is physically cycled — most reliably triggered by a polkit password dialog (easy to reproduce with pkexec true). Confirmed this isn't fixable via config: numlock_by_default only seeds a device's state at connect/session-start, and reissuing it live (hyprctl eval 'hl.config({input={numlock_by_default=true}})') does nothing once devices are already desynced — the actual lock state lives in Hyprland's internal per-device xkb objects, invisible to any hyprctl command. Matches several already-closed-as-"not planned" upstream issues (#9575, #6886, #8288), so this looks like a known architectural limitation around multi-device keyboard state tracking rather than something Omarchy's config can work around.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
Not linked to any known issue, other report or change yet.
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.