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-5332GitHub issuePublicDecided· Out of scope

Keyboard layout chosen in installer isn't applied to Hyprland/fcitx5 — desktop falls back to US

Reported by Ambulog · filed Oct 11, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 26 h ago.

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?
AreaOutside the audited area· 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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Keyboard layout chosen in installer isn't applied to Hyprland/fcitx5 — desktop falls back to USrevision 1 · captured 2026-10-11 10:10 UTC via poll

Keyboard layout chosen during install isn't used in Hyprland/fcitx5. Desktop falls back to US

What happened

During installation I selected Swiss German as the keyboard layout. The installer used that layout correctly. After the first boot into the desktop, though, the keyboard was US English everywhere.

Expected

The layout chosen in the installer should also be the layout in Hyprland and fcitx5.

Cause (as far as I can tell)

/etc/vconsole.conf after install only has the console keymap. It has no XKB layout:

KEYMAP=de_CH-latin1
FONT=default8x16

localectl status shows X11 Layout: (unset).

default/hypr/input.lua builds kb_layout from vconsole.XKBLAYOUT or "us". With XKBLAYOUT missing, Hyprland falls back to us.

There's also a second problem. fcitx5 runs (omarchy-fcitx5.service) but there's no ~/.config/fcitx5/profile, so it uses its default keyboard-us input method. Its virtual keyboard (hl-virtual-keyboard-fcitx5) stayed on l "us" even after I set kb_layout = "ch" in Hyprland. Both had to be fixed before typing actually used Swiss German.

Steps to reproduce

  1. Install Omarchy and choose a non-US keyboard layout (e.g. Swiss German) in the installer.
  2. Boot into the desktop.
  3. Type: the layout is US. hyprctl devices shows l "us".

Suggested fix

  • Have the installer also write XKBLAYOUT/XKBVARIANT to /etc/vconsole.conf, for example with localectl set-keymap (which converts to X11 by default) or localectl set-x11-keymap ch de. Another option is to map KEYMAP to an XKB layout in input.lua when XKBLAYOUT is missing.
  • Generate ~/.config/fcitx5/profile from the same layout so fcitx5 doesn't default to keyboard-us.

Workaround

  • ~/.config/hypr/input.lua: hl.config({ input = { kb_layout = "ch", kb_variant = "de" } })
  • ~/.config/fcitx5/profile with DefaultIM=keyboard-ch-de, then restart fcitx5.

System

  • Omarchy 4.0.4-1
  • Lenovo ThinkPad, built-in keyboard (at-translated-set-2-keyboard)
  • Kernel 7.2.5-3-omarchy
View raw text
## Keyboard layout chosen during install isn't used in Hyprland/fcitx5. Desktop falls back to US

### What happened
During installation I selected **Swiss German** as the keyboard layout. The installer used that layout correctly. After the first boot into the desktop, though, the keyboard was **US English** everywhere.

### Expected
The layout chosen in the installer should also be the layout in Hyprland and fcitx5.

### Cause (as far as I can tell)
`/etc/vconsole.conf` after install only has the console keymap. It has no XKB layout:

```
KEYMAP=de_CH-latin1
FONT=default8x16
```

`localectl status` shows `X11 Layout: (unset)`.

`default/hypr/input.lua` builds `kb_layout` from `vconsole.XKBLAYOUT or "us"`. With `XKBLAYOUT` missing, Hyprland falls back to `us`.

There's also a second problem. fcitx5 runs (`omarchy-fcitx5.service`) but there's no `~/.config/fcitx5/profile`, so it uses its default `keyboard-us` input method. Its virtual keyboard (`hl-virtual-keyboard-fcitx5`) stayed on `l "us"` even after I set `kb_layout = "ch"` in Hyprland. Both had to be fixed before typing actually used Swiss German.

### Steps to reproduce
1. Install Omarchy and choose a non-US keyboard layout (e.g. Swiss German) in the installer.
2. Boot into the desktop.
3. Type: the layout is US. `hyprctl devices` shows `l "us"`.

### Suggested fix
- Have the installer also write `XKBLAYOUT`/`XKBVARIANT` to `/etc/vconsole.conf`, for example with `localectl set-keymap` (which converts to X11 by default) or `localectl set-x11-keymap ch de`. Another option is to map `KEYMAP` to an XKB layout in `input.lua` when `XKBLAYOUT` is missing.
- Generate `~/.config/fcitx5/profile` from the same layout so fcitx5 doesn't default to `keyboard-us`.

### Workaround
- `~/.config/hypr/input.lua`: `hl.config({ input = { kb_layout = "ch", kb_variant = "de" } })`
- `~/.config/fcitx5/profile` with `DefaultIM=keyboard-ch-de`, then restart fcitx5.

### System
- Omarchy 4.0.4-1
- Lenovo ThinkPad, built-in keyboard (`at-translated-set-2-keyboard`)
- Kernel 7.2.5-3-omarchy

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.

  • Out of scopeDecided by agents · verified · 2026-10-11 10:16 UTC