Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1146GitHub issuePublicDecided· Out of scope

Keyboard layout mismatch between installation and login

Reported by anthony-robin · filed Aug 31, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Keyboard layout mismatch between installation and loginrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Intel Core Ultra 7, Omarchy 4.0, french AZERTY keyboard

What's wrong?

During the initial Omarchy installation, I was using a French keyboard layout and chose a password containing accented/special characters.

The installation completed successfully, but once I reached the login screen, my password was not accepted. I had to reformat/reinstall Omarchy and choose a simpler password without those characters.

This makes me wonder whether the keyboard layout selected during the installation is correctly preserved between the account/password creation step and the first login after installation.

It would be worth checking whether the keyboard layout or input configuration can change between these two stages. In particular, passwords containing characters that differ between keyboard layouts (e.g. French AZERTY vs US QWERTY) could make this issue particularly difficult to diagnose, since the password appears to have been accepted during installation but then fails at login.

It would be great if the installer could ensure that the exact same keyboard layout is active during the first login, or warn the user about potential issues with special characters in passwords.

Thanks !

View raw text
### System details

Intel Core Ultra 7, Omarchy 4.0, french AZERTY keyboard

### What's wrong?

During the initial Omarchy installation, I was using a French keyboard layout and chose a password containing accented/special characters.

The installation completed successfully, but once I reached the login screen, my password was not accepted. I had to reformat/reinstall Omarchy and choose a simpler password without those characters.

This makes me wonder whether the keyboard layout selected during the installation is correctly preserved between the account/password creation step and the first login after installation.

It would be worth checking whether the keyboard layout or input configuration can change between these two stages. In particular, passwords containing characters that differ between keyboard layouts (e.g. French AZERTY vs US QWERTY) could make this issue particularly difficult to diagnose, since the password appears to have been accepted during installation but then fails at login.

It would be great if the installer could ensure that the exact same keyboard layout is active during the first login, or warn the user about potential issues with special characters in passwords.

Thanks !

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 10:19 UTC