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.
Keyboard Layout Automation
Reported by islamqasimov · filed Oct 26, 2025Closed upstream on 2026-02-01. 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
What do you need?
Summary
Omarchy currently lacks a built-in keyboard layout switching mechanism, requiring users to manually add and configure layouts via system settings or Waybar. However, this limitation causes a critical usability issue during the authentication phase after auto logout.
Problem Description
When the system automatically logs out, it remembers the last active keyboard layout. During the next login attempt, the authentication screen uses this remembered layout, but does not provide any visible option to change it.
As a result, if the user had previously switched to a non-default layout (e.g., from English to another language), typing their password on the login screen may fail because the input layout differs from what they expect. The system will then throw an “**Authentication Failed**” error.
Since layout switching is unavailable on the login screen, the user is forced to reboot to regain access.
View raw text
### What do you need? ### Summary Omarchy currently lacks a built-in keyboard layout switching mechanism, requiring users to manually add and configure layouts via system settings or Waybar. However, this limitation causes a critical usability issue during the authentication phase after auto logout. ### Problem Description When the system automatically logs out, it remembers the last active keyboard layout. During the next login attempt, the authentication screen uses this remembered layout, but does not provide any visible option to change it. As a result, if the user had previously switched to a non-default layout (e.g., from English to another language), typing their password on the login screen may fail because the input layout differs from what they expect. The system will then throw an “_**Authentication Failed**_” error. Since layout switching is unavailable on the login screen, the user is forced to reboot to regain access.
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.