OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core high common DISPUTE

Unlock an account faillock locked after failed password attempts

omarchyarchendeavouroscachyosmanjaro
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Substantially correct: manual/45-troubleshooting.md gives almost this exact procedure (CTRL + ALT + F2, login as root, faillock --reset --user [your-username]). Two gaps. (1) It omits the single most useful fact: bin/omarchy-apply-lock configures pam_faillock with deny=10 unlock_time=120, so the lockout clears itself after two minutes. Most users just need to wait rather than drop to a TTY. (2) The keyboard-layout remedy uses the obsolete .conf format. Current Omarchy uses ~/.config/hypr/input.lua with an hl.config() call. Minor caveat worth adding: logging in as root at the TTY only works if a root password was actually set.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

After mistyping the password a few times, the login screen (or sudo) rejects even the correct password. su reports Account locked due to N failed logins, or authentication just silently fails every time.

Cause

PAM's pam_faillock has locked the account after repeated failed authentications. It stays locked until the deny window expires or the counter is reset. Very common right after an install where the keyboard layout defaulted to a different one than the user typed the password in.

Fix

Omarchy configures pam_faillock with deny=10 unlock_time=120, so the simplest fix is to **wait two minutes** and try again. The lockout expires on its own.

If you do not want to wait, switch to a text console with Ctrl + Alt + F2 and log in as **root** (this requires a root password to have been set), then reset the counter:


faillock --user yourusername --reset

Check the state first if you want:


faillock --user yourusername

If root has no password, log in as your own user on the TTY once the 120s window has expired and run it with sudo:


sudo faillock --user yourusername --reset

Then Ctrl + Alt + F1 back to the graphical session.

If the underlying cause was a wrong keyboard layout at the login screen, fix it in ~/.config/hypr/input.lua:


hl.config({
  input = {
    kb_layout = "us",
  },
})

(On an older Omarchy 3 install this is ~/.config/hypr/input.conf using the input { kb_layout = us } block syntax.) Apply with hyprctl reload.

Verify

faillock --user yourusername reports no failures and the normal password works at the login screen.

Sources

locked-out-faillock-too-many-attempts