Fix the lock screen and polkit rejecting a correct password on a non-US layout
Issue #8060 (open) Bug A and its comments support every part of the record: the fcitx5 profile with only keyboard-us on a fr or es install, QT_IM_MODULE=fcitx routing the Quickshell lock and polkit fields through fcitx5, wake from sleep only exposing it, the polkit-1 pam_unix authentication failure next to a working sudo, and the stop, edit, start order because restart reverts the profile. Issue #7049 and its comment confirm the hardcoded keyboard-us profile on fresh installs and the keyboard-ch-de_mac variant naming with fcitx5-remote -n. Confirmed on this workstation: /usr/lib/environment.d/10-omarchy-fcitx.conf sets QT_IM_MODULE=fcitx, ~/.config/fcitx5/profile holds only keyboard-us, nothing in /usr/share/omarchy writes DefaultIM, so the profile is fcitx5's own default, omarchy-system-lock exists, and both system-auth and omarchy-lock-password run pam_faillock deny=10 unlock_time=120, which matches the danger. PR #12920 (seed DefaultIM from vconsole) is open, so the bug is current on 4.0.4. Not exercised: editing the profile, locking, or switching to a TTY while the lock screen holds focus.
Repeated wrong attempts at the lock screen trigger a two-minute lockout after ten failures. Fix the profile from a terminal or TTY rather than retrying at the prompt.
Symptom
On a French, Spanish, German or other non-US Omarchy 4 install, the lock screen (especially after waking from sleep) and the polkit dialog reject the correct password, while sudo in a terminal accepts the same password seconds later. journalctl shows pam_unix(polkit-1:auth): authentication failure. hyprctl devices and localectl status both show the correct layout, so it looks like a corrupted password or faillock.
Cause
The lock screen and the polkit agent are Quickshell (Qt) text fields, and QT_IM_MODULE=fcitx routes their keystrokes through fcitx5. On many installs ~/.config/fcitx5/profile was generated with DefaultIM=keyboard-us and only a keyboard-us item, regardless of /etc/vconsole.conf (XKBLAYOUT=fr). So Qt fields type US while the compositor and terminals type the real layout. Waking from sleep only makes it visible, because the password field is the first text input focused after resume.
Fix
Point fcitx5's default group at your layout. Stop fcitx5 before editing, because it overwrites the file with its in-memory state when it exits (restart reverts the edit):
grep -E 'XKB' /etc/vconsole.conf # e.g. XKBLAYOUT=fr
systemctl --user stop omarchy-fcitx5.service
# ~/.config/fcitx5/profile
[Groups/0]
Name=Default
Default Layout=fr
DefaultIM=keyboard-fr
[Groups/0/Items/0]
Name=keyboard-fr
[GroupOrder]
0=Default
For a variant the name is keyboard-<layout>-<variant>, for example keyboard-ch-de_mac with Default Layout=ch-de_mac.
systemctl --user start omarchy-fcitx5.service
fcitx5-remote -n # should print keyboard-fr
If you are locked out right now: switch to a TTY (Ctrl+Alt+F3) or ssh in, log in as the same user, and run the stop, edit, start sequence there. Typing the password using US key positions at the lock screen also works as a one-off.
Verify
fcitx5-remote -n prints your layout's keyboard-* name. Run pkexec true and authenticate with a password containing layout-specific characters. Lock with omarchy-system-lock and unlock.