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.
Can't put complex name of the layout format, e.g. format-us_fr-qwerty
Reported by DarkzAtom · filed Dec 2, 2025Closed upstream on 2025-12-08 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
PC: ROG Strix G713QR_G713QR (1.0) | CPU: AMD Ryzen 7 5800H (16) @ 4.46 GHz | GPU: NVIDIA GeForce RTX 3070 Mobile / Max-Q [Discrete] & AMD Radeon Vega Series [Integrated] | Display: 2560x1440 @ 1.6x in 17", 165 Hz [Built-in] | Storage: 86.87 GiB / 105.82 GiB (82%) - btrfs | Memory: 5.37 GiB / 15.04 GiB (36%) | Battery: Disabled | OS: Omarchy 3.2.2 (master/stable) | Kernel: Linux 6.17.9-arch1-1 | WM: Hyprland 0.52.1 (Wayland) | Terminal: alacritty 0.16.1 | Packages: 1254 (pacman) | Theme: Everforest | Font: alacritty (9pt)
What's wrong?
PROBLEM: Refuses to work with complex name of the layout.
DESCRIPTION: I have a layout config that looks like this:
~/.config/hypr/input.conf
...
input {
\# Use multiple keyboard layouts and switch between them with Left Alt + Right Alt
kb_layout = pl,ru,us_qwerty-fr
kb_options = compose:caps,grp:alt_shift_toggle # alt_altgr_toggle
\# resolve_binds_by_sym = true
...
And in my waybar config it works perfectly fine for PL and RU, however not for us_qwerty-fr. This is how I have it:
~/.config/waybar/config.jsonc
...
"hyprland/language": {
"format": "{}",
"format-en": "US",
"format-pl": "PL",
"format-ru": "RU",
"format-us_qwerty-fr": "FRUS"
}, ...
View raw text
### System details
PC: ROG Strix G713QR_G713QR (1.0) | CPU: AMD Ryzen 7 5800H (16) @ 4.46 GHz | GPU: NVIDIA GeForce RTX 3070 Mobile / Max-Q [Discrete] & AMD Radeon Vega Series [Integrated] | Display: 2560x1440 @ 1.6x in 17", 165 Hz [Built-in] | Storage: 86.87 GiB / 105.82 GiB (82%) - btrfs | Memory: 5.37 GiB / 15.04 GiB (36%) | Battery: Disabled | OS: Omarchy 3.2.2 (master/stable) | Kernel: Linux 6.17.9-arch1-1 | WM: Hyprland 0.52.1 (Wayland) | Terminal: alacritty 0.16.1 | Packages: 1254 (pacman) | Theme: Everforest | Font: alacritty (9pt)
### What's wrong?
PROBLEM: Refuses to work with complex name of the layout.
DESCRIPTION: I have a layout config that looks like this:
~/.config/hypr/input.conf
...
input {
\# Use multiple keyboard layouts and switch between them with Left Alt + Right Alt
kb_layout = pl,ru,us_qwerty-fr
kb_options = compose:caps,grp:alt_shift_toggle # alt_altgr_toggle
\# resolve_binds_by_sym = true
...
And in my waybar config it works perfectly fine for PL and RU, however not for us_qwerty-fr. This is how I have it:
~/.config/waybar/config.jsonc
...
"hyprland/language": {
"format": "{}",
"format-en": "US",
"format-pl": "PL",
"format-ru": "RU",
"format-us_qwerty-fr": "FRUS"
}, ...
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.