basecamp
Authentication failure via lock screen after some X amount of time
System details
AMD 7 5800X, RTX 3070Ti, Omarchy v3.0.2
What's wrong?
I've ran into this issue a handful of times where if I lock the screen and come back an hour or so later I am unable to log in and get the Authentication failed message.
related to nvda?
I noticed that after the system wakes up after suspending, the login screen (hyprlock) takes some time to load completly, and if you type something too fast hyperlock does not record the first character entered - mb this is your issue ?
I've been having the same issue. After leaving my desktop unattended for a while I come back and am unable to login. I try multiple attempts but can't sign in. Only solution is to restart my PC. I have AMD tho.
+1 I can also confirm the bug, but I cannot reliably tell what exactly causes it. I faced a few times after suspending the system.
@rsd mentioned in discussions:
More specifically pam_faillock.so (in /etc/pam.d/system-auth).
After a few wrong passwords, it will lock you out for sometime (unlock_time) even with the correct password, even in the console. The sensation is that some auth service crashed or the system got corrupted.
Will look in to this as I have a teenie-tiny bit of exp. with systemd-cryptenroll and pamu2f. If anyone finds a way to intentionally re-create this problem please post here.
I have a Integrated Fingerprint Reader on my Lenovo thinkpad. I have not configured it but wondered somehow if any of the others with the same issue are similar? Mike
🧱 Hyprlock PAM Unlock Issue on Omarchy
Noticed that Hyprlock can’t unlock with the correct password on current Omarchy builds.
This appears to come from a missing /etc/pam.d/hyprlock service file in the Arch base image.
🔍 Likely Cause
Without a PAM policy, Hyprlock doesn’t know how to authenticate — it just fails silently.
Upstream Arch recently added this file in their official package, so it may simply be a version gap.
🩹 Temporary Fix
You can restore normal unlock behavior by adding the missing PAM entry, then restarting your user session:
sudo tee /etc/pam.d/hyprlock >/dev/null <<'EOF'
# Omarchy PAM fix for Hyprlock (Arch-based)
auth include system-local-login
account include system-local-login
password include system-local-login
session include system-local-login
EOF
systemctl --user restart hyprland.service
🧩 Reference
Arch package reference (as of hyprlock 0.8.2-1):
https://archlinux.org/packages/extra/x86_64/hyprlock/files/
✅ Upstream Note
Once Omarchy rebases onto a newer Arch snapshot that includes this version, the issue should resolve automatically.
Until then, the above workaround restores expected PAM authentication.
When I run
systemctl --user restart hyprland.service
I get the error:
Failed to restart hyprland.service: Unit hyprland.service not found.
The following worked:
systemctl --user restart [email protected]
I have this situation too, on other distros i will restart it and it work again. but on this omarchy, i can't enter with my password after reboot.
My solution is restart and use snapshot version, and it work again.
i don't know where the problem is, but before i had that situation, i install many program. I hope my story help some people who got to this situation too
Same issue here, after it wakes up, it asks for a password but shows “Authentication Failed.” Is there a way to open the terminal and reboot or debug the issue? Has anyone found a solution?
I have founded this open thread in Hyprlock https://github.com/hyprwm/hyprlock/issues/499
and with ChatGPT’s help, I fixed my issue by resetting the lockout timer.
Switch to a TTY
Press Ctrl + Alt + F2 (or F3/F4) → log in with your user.
Check & clear PAM faillock
# See if you’re locked out
faillock --user "$USER"
# If there are records or a lockout timer, reset them:
sudo faillock --user "$USER" --reset
The full response: https://chatgpt.com/s/t_68fb20fc2d508191a320c078fe8c0d7d
You can restore normal unlock behavior by adding the missing PAM entry, then restarting your user session:
sudo tee /etc/pam.d/hyprlock >/dev/null <<'EOF' # Omarchy PAM fix for Hyprlock (Arch-based) auth include system-local-login account include system-local-login password include system-local-login session include system-local-login EOF
This solves the problem for me. Cheers, @ItsMick!
Dang, I tried all fixes and none of them work. I could login on another TTY, but hyprlock just never authenticated me
I got an issue in the UI lock screen, it won't allow me to pass with, what I think it was the correct password. 20 times or so. I had to reboot to be able to get in.
I'm seeing a similar issue with credential validation failing when trying to install something from aur after sometime, that requires a reboot to fix. I wonder if this is a related problem or something different.
To be fair, this isn’t an Omarchy issue, it’s strictly a Hyprland one. For a proper fix, the issue likely needs to be raised upstream.