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.
Initial log-in screen recognizes the backspace key as a password character, and other similar keyboard problems
Reported by ghost · filed Sep 28, 2025Closed upstream on 2025-11-14. 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
i7-1270p, iGPU, Omarchy 3.0.1
What's wrong?
The initial log-in screen when you boot up the computer detects the backspace key that you wold use to delete a mistyped character is instead recognized (shows up) as an additional character, which makes entering the password more challenging.
My keyboard layout is a Lenovo Turkish ISO QWERTY layout. Could that be the problem?
Interestingly, this is not a problem after the initial log-in , when you just lock the computer.
Furthermore, this is not the only keyboard problem I've experienced with Omarchy. Specifically, after I installed Arch Linux, either while logging into my account to type in the bash command to install Omarchy, or a little after that (can't remember the whole install process), the layout reverted to a US ISO layout, which made typing the password extremely frustrating (I had to delete my Arch install and re-install everything again 3 times because I couldn't understand that the layout switching was the issue and thought I mistyped my password during the account creation instead).
After that saga, during the whole uwsm outage, I couldn't enter the systemd.unit=single-user.target command in the bootloader after pressing 'e' to get around that issue, because for some reason the 'i' key in my keyboard was disabled.
I still like Omarchy even after all of this, but I pray that an issue like the uwsm one will not happen again because I might get locked out of my account next time.
View raw text
### System details i7-1270p, iGPU, Omarchy 3.0.1 ### What's wrong? The initial log-in screen when you boot up the computer detects the backspace key that you wold use to delete a mistyped character is instead recognized (shows up) as an additional character, which makes entering the password more challenging. My keyboard layout is a Lenovo Turkish ISO QWERTY layout. Could that be the problem? Interestingly, this is not a problem after the initial log-in , when you just lock the computer. Furthermore, this is not the only keyboard problem I've experienced with Omarchy. Specifically, after I installed Arch Linux, either while logging into my account to type in the bash command to install Omarchy, or a little after that (can't remember the whole install process), the layout reverted to a US ISO layout, which made typing the password extremely frustrating (I had to delete my Arch install and re-install everything again 3 times because I couldn't understand that the layout switching was the issue and thought I mistyped my password during the account creation instead). After that saga, during the whole uwsm outage, I couldn't enter the `systemd.unit=single-user.target` command in the bootloader after pressing 'e' to get around that issue, because for some reason the 'i' key in my keyboard was disabled. I still like Omarchy even after all of this, but I pray that an issue like the uwsm one will not happen again because I might get locked out of my account next time.
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.