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.
Choosing non-English layout in installation makes the system unusable
Reported by Cutipus · filed Jun 13, 2026Closed upstream on 2026-07-27 by the merge of PR #6344 (closed by dhh). 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
Omarchy 3.8.2
What's wrong?
I tried to install Omarchy on a new machine, and during installation chose a non-English keyboard layout (Hebrew) as my default keyboard layout, assuming it would save me the trouble of editing input.conf and setting everything up. Turns out that if you do that you wont have an English layout at all to work with, and therefore not be able to properly edit the config in the first place to add English. Many keybinds (such as closing windows) wont work either, meaning your system is essentially left in a non-operational state after choosing such a layout.
Many of Omarchy's keybinds are defined in terms of English letters (keysyms):
# Close windows
bindd = SUPER, W, Close window, killactive,
bindd = CTRL ALT, DELETE, Close all windows, exec, omarchy-hyprland-window-close-all
# Control tiling
bindd = SUPER, J, Toggle window split, layoutmsg, togglesplit
bindd = SUPER, P, Pseudo window, pseudo, # dwindle
bindd = SUPER, T, Toggle window floating/tiling, togglefloating,
bindd = SUPER, F, Full screen, fullscreen, 0
bindd = SUPER CTRL, F, Tiled full screen, fullscreenstate, 0 2
bindd = SUPER ALT, F, Full width, fullscreen, 1
bindd = SUPER, O, Pop window out (float & pin), exec, omarchy-hyprland-window-pop
bindd = SUPER, L, Toggle workspace layout, exec, omarchy-hyprland-workspace-layout-toggle(.local/share/omarchy/default/hypr/bindings/tiling-v2.conf)
Which means all of these fail to work on non-English layouts.
Suggestions to fix:
1. Treat the installation option of choosing a keyboard layout as an optional secondary option, where English is the default and always installed. If you choose a secondary layout, automatically enable grp:... in input.conf to allow switching between them. This would ensure the system is always in a working state after installation.
2. Change all keysyms (SUPER, J, ...) to keycodes (SUPER, code:44, ...) which are layout-agnostic and would ensure the basic keybindings work even on different non-English layouts. These codes could be found using the wev command. Seeing as how many keybinds already use this code:... form, I think it would also be more consistent to do that.
View raw text
### System details Omarchy 3.8.2 ### What's wrong? I tried to install Omarchy on a new machine, and during installation chose a non-English keyboard layout (Hebrew) as my default keyboard layout, assuming it would save me the trouble of editing `input.conf` and setting everything up. Turns out that if you do that you wont have an English layout at all to work with, and therefore not be able to properly edit the config in the first place to add English. Many keybinds (such as closing windows) wont work either, meaning your system is essentially left in a non-operational state after choosing such a layout. Many of Omarchy's keybinds are defined in terms of English letters (keysyms): ```hypr # Close windows bindd = SUPER, W, Close window, killactive, bindd = CTRL ALT, DELETE, Close all windows, exec, omarchy-hyprland-window-close-all # Control tiling bindd = SUPER, J, Toggle window split, layoutmsg, togglesplit bindd = SUPER, P, Pseudo window, pseudo, # dwindle bindd = SUPER, T, Toggle window floating/tiling, togglefloating, bindd = SUPER, F, Full screen, fullscreen, 0 bindd = SUPER CTRL, F, Tiled full screen, fullscreenstate, 0 2 bindd = SUPER ALT, F, Full width, fullscreen, 1 bindd = SUPER, O, Pop window out (float & pin), exec, omarchy-hyprland-window-pop bindd = SUPER, L, Toggle workspace layout, exec, omarchy-hyprland-workspace-layout-toggle ``` (`.local/share/omarchy/default/hypr/bindings/tiling-v2.conf`) Which means all of these fail to work on non-English layouts. Suggestions to fix: 1. Treat the installation option of choosing a keyboard layout as an optional secondary option, where English is the default and always installed. If you choose a secondary layout, automatically enable `grp:...` in `input.conf` to allow switching between them. This would ensure the system is always in a working state after installation. 2. Change all keysyms (`SUPER, J, ...`) to keycodes (`SUPER, code:44, ...`) which are layout-agnostic and would ensure the basic keybindings work even on different non-English layouts. These codes could be found using the `wev` command. Seeing as how many keybinds already use this `code:...` form, I think it would also be more consistent to do that.
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.