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-2621GitHub issuePublicReceived

[bug] Omarchy/hyprland install overrides arch install keyboard layout

Reported by benWindsorCode · filed Aug 25, 2025Closed upstream on 2025-08-31 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

[bug] Omarchy/hyprland install overrides arch install keyboard layoutrevision 1 · captured 2026-10-04 11:27 UTC via poll

In the arch setup process you pick a keyboard layout and language (in my case GB keyboard).

However whatever you pick is overridden after the omarchy install runs by the default in:
~/.local/share/omarchy/default/hypr/input.conf (and user can then override in ~/.config/hypr/input.conf)

While it's an easy fix to then update the config, the confusion comes from the fact that the underlying arch settings are still correct. If you run (per the arch wiki) 'localectl status' it will still show you (now overridden) the key binds from the install - even though in reality these are getting overridden by omarchy+hyperland setup process.

Not a major issue but one that can trip up new users like myself from an otherwise very smooth onboard process.

Side note: love the project, thanks for all the hard work

View raw text
In the arch setup process you pick a keyboard layout and language (in my case GB keyboard). 

However whatever you pick is overridden after the omarchy install runs by the default in:
~/.local/share/omarchy/default/hypr/input.conf (and user can then override in ~/.config/hypr/input.conf)

While it's an easy fix to then update the config, the confusion comes from the fact that the underlying arch settings are still correct. If you run (per the arch wiki) 'localectl status' it will still show you (now overridden) the key binds from the install - even though in reality these are getting overridden by omarchy+hyperland setup process. 

Not a major issue but one that can trip up new users like myself from an otherwise very smooth onboard process. 

Side note: love the project, thanks for all the hard work 

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.