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.
German keyboard layout in live installer uses keymap without umlauts
Reported by Witteborn · filed Aug 27, 2026 · open at source
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
System details
AMD Ryzen AI 9 365, AMD Radeon 880M, Omarchy 4.0.1-1, kernel 7.1.9-arch1-2
What's wrong?
Selecting German in the live installer does not provide the standard German keyboard layout. The ä, ö, and ü keys cannot be typed correctly. Selecting German (Switzerland) makes the umlauts available, but special characters such as @ then follow the Swiss layout. After installation and reboot, the normal German layout works correctly, including the umlauts and AltGr+Q for @.
Steps to reproduce:
- Boot the Omarchy installation ISO.
- Select German as the keyboard layout.
- Continue to a text field such as the name or password field.
- Try to enter
ä,ö,ü, and@. - Repeat with German (Switzerland).
Expected: German uses the standard German layout during installation, with ä, ö, ü, and AltGr+Q for @.
The shared setup form currently maps the choice to the console keymap de:
German|de
German (Switzerland)|de_CH-latin1The ISO configurator then applies it with loadkeys "$keyboard". In the Arch kbd keymap, de maps the physical umlaut keys to characters such as @, [ and ]. The standard German console keymap is de-latin1, which maps those keys to udiaeresis, odiaeresis, and adiaeresis and keeps AltGr+Q as @.
Changing the entry to German|de-latin1 also preserves the installed desktop layout: systemd-firstboot --keymap=de-latin1 writes KEYMAP=de-latin1 and XKBLAYOUT=de.
View raw text
### System details AMD Ryzen AI 9 365, AMD Radeon 880M, Omarchy 4.0.1-1, kernel 7.1.9-arch1-2 ### What's wrong? Selecting **German** in the live installer does not provide the standard German keyboard layout. The `ä`, `ö`, and `ü` keys cannot be typed correctly. Selecting **German (Switzerland)** makes the umlauts available, but special characters such as `@` then follow the Swiss layout. After installation and reboot, the normal German layout works correctly, including the umlauts and `AltGr+Q` for `@`. Steps to reproduce: 1. Boot the Omarchy installation ISO. 2. Select **German** as the keyboard layout. 3. Continue to a text field such as the name or password field. 4. Try to enter `ä`, `ö`, `ü`, and `@`. 5. Repeat with **German (Switzerland)**. Expected: **German** uses the standard German layout during installation, with `ä`, `ö`, `ü`, and `AltGr+Q` for `@`. The shared setup form currently maps the choice to the console keymap `de`: ```bash German|de German (Switzerland)|de_CH-latin1 ``` The ISO configurator then applies it with `loadkeys "$keyboard"`. In the Arch `kbd` keymap, `de` maps the physical umlaut keys to characters such as `@`, `[` and `]`. The standard German console keymap is `de-latin1`, which maps those keys to `udiaeresis`, `odiaeresis`, and `adiaeresis` and keeps `AltGr+Q` as `@`. Changing the entry to `German|de-latin1` also preserves the installed desktop layout: `systemd-firstboot --keymap=de-latin1` writes `KEYMAP=de-latin1` and `XKBLAYOUT=de`.
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-09 09:41 UTC