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.
SDDM greeter's Hyprland config ignores system keyboard layout, causing password mismatches for non-US layouts
Reported by winless-code · filed Aug 31, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #6880 (R-1858). 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
Title: SDDM greeter's Hyprland config ignores system keyboard layout, causing password mismatches for non-US layouts
What happened
The SDDM Wayland greeter runs its own minimal Hyprland instance via/usr/share/sddm/hyprland.lua (referenced from/etc/sddm.conf.d/10-wayland.conf as CompositorCommand). This config has
no input block, so it falls back to Hyprland's default keyboard layout
(US), regardless of the system's actually configured layout
(localectl correctly reports de for both console and X11).
This is invisible for most passwords, but any password containing a
character that sits on a different key between the US and configured
layout (e.g. _ on a US vs. German keyboard) gets typed incorrectly at
the greeter — while working fine on a TTY or inside the real Hyprland
session, since those correctly use the system layout.
What was expected
The SDDM greeter should use the system's configured keyboard layout
(as reported by localectl status), matching what the TTY and the
user's actual Hyprland session use — so password entry is consistent
across all three.
Steps to reproduce
- Install Omarchy on a system with a non-US keyboard layout (e.g.
de)
configured via localectl / /etc/vconsole.conf.
2. Set a password containing a character that differs in position between
the US and configured layout (e.g. _, which is Shift+Minus on US but
a different key combination on German layout).
3. Reboot to the SDDM login screen and enter the password.
4. Login fails — the greeter's default US-layout Hyprland instance
produces the wrong character(s). Password verified independently
(e.g. via openssl passwd -6 against /etc/shadow) confirms it's
correct; entering the same password on a TTY works.
Workaround
Manually add an input block to /usr/share/sddm/hyprland.lua:
hl.config({
input = { kb_layout = 'de' },
...
})This is not durable: the file is owned by the omarchy-settings package
and has no pacman backup/pacnew protection, so it is silently overwritten
(and the bug reintroduced) on the next omarchy update.
System details
- Omarchy version: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
- GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] (i915 driver)
- Keyboard layout: de (confirmed via
localectl status: VC Keymap, X11 Layout bothde)
View raw text
Title: SDDM greeter's Hyprland config ignores system keyboard layout, causing password mismatches for non-US layouts
## What happened
The SDDM Wayland greeter runs its own minimal Hyprland instance via
`/usr/share/sddm/hyprland.lua` (referenced from
`/etc/sddm.conf.d/10-wayland.conf` as `CompositorCommand`). This config has
no `input` block, so it falls back to Hyprland's default keyboard layout
(US), regardless of the system's actually configured layout
(`localectl` correctly reports `de` for both console and X11).
This is invisible for most passwords, but any password containing a
character that sits on a different key between the US and configured
layout (e.g. `_` on a US vs. German keyboard) gets typed incorrectly at
the greeter — while working fine on a TTY or inside the real Hyprland
session, since those correctly use the system layout.
## What was expected
The SDDM greeter should use the system's configured keyboard layout
(as reported by `localectl status`), matching what the TTY and the
user's actual Hyprland session use — so password entry is consistent
across all three.
## Steps to reproduce
1. Install Omarchy on a system with a non-US keyboard layout (e.g. `de`)
configured via `localectl` / `/etc/vconsole.conf`.
2. Set a password containing a character that differs in position between
the US and configured layout (e.g. `_`, which is Shift+Minus on US but
a different key combination on German layout).
3. Reboot to the SDDM login screen and enter the password.
4. Login fails — the greeter's default US-layout Hyprland instance
produces the wrong character(s). Password verified independently
(e.g. via `openssl passwd -6` against `/etc/shadow`) confirms it's
correct; entering the same password on a TTY works.
## Workaround
Manually add an `input` block to `/usr/share/sddm/hyprland.lua`:
```lua
hl.config({
input = { kb_layout = 'de' },
...
})
```
This is not durable: the file is owned by the `omarchy-settings` package
and has no pacman backup/pacnew protection, so it is silently overwritten
(and the bug reintroduced) on the next `omarchy update`.
## System details
- Omarchy version: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
- GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] (i915 driver)
- Keyboard layout: de (confirmed via `localectl status`: VC Keymap, X11 Layout both `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.
No decision has been recorded yet.