Swaylock requires (or appears to require) multiple attempts with correct password to unlock

[crawfordlong]

I have used swaylock successfully with sway for some time, to the degree that I don't actually know where to find logfiles, etc. to troubleshoot issues. My current testing setup is giving me issues however:

Environment:
Fedora Silverblue 37
swaylock 1.7.2 (layered on base system)
hyprland WM 0.23beta

Idle config located at ~/.config/swayidle/config; swayidle executed with swayidle -w (manually testing) or exec-once=swayidle -w (WM config). swayidle is launching correctly in each case and appears to be triggering swaylock based on (a) setting idle timer to a short time and waiting and (b) closing my laptop lid. What I can't tell is whether this is a quirk of Silverblue (swaylock having an issue with something on the immutable part of the system), hyprland (obviously under rapid and early development, and possibly missing or misfiring an event), or swaylock.

Expected Behavior:
Upon command (i.e., bound key such as SUPER+L), swayidle timer, or event (laptop lid closed), execute swaylock -f -c #000000, which locks the display and may perform other actions such as turning off the display. Appropriate action, such as tapping a key or opening the laptop lid displays the unlock screen, and typing the user password immediately unlocks the laptop.

Observed Behavior:
Swayidle and other events appear to correctly trigger swaylock, including related activities such as turning off the display. Waking (or returning to) the locked device appears to correctly show the lock screen. The lock screen appears to correctly receive inputs while typing (there's no stuttering or flickering indicating a possible input problem). However, the "Verifying" step sometimes times out, and it takes as many as 7-10 correct password entries (or, at least, verifying they are typed correctly by me) before the unlock will occur. Failed attempts do not display any error or warning at all. Sometime, though I haven't been able to repeat this consistently, it almost seems like the unlock and validation is happening but very, very slowly, so typing the password > validation > time passes > unlock successful.

[kennylevinsen]

All verification is done by PAM. You may have an issue in your PAM stack used for swaylock.

[plum]

I have the same issue with swaylock on an arch distro, actullay two on eon desktop one on laptop, and th edesktop is a fresh install.

Moreover I never get a sucussful login attempt. Yes, it will be a pam issue. However , I have no problem logging on with a tui login greeter, freetd. THis uses the /etc/pam.d/login file, as does swaylock , to the best of my knowledge.

I used to be able to use swaylock, two years ago.

BY contrast, waylock work fine with my pam stack, when directed to use the pam.d/login file.

[kennylevinsen]

THis uses the /etc/pam.d/login file, as does swaylock , to the best of my knowledge.

Swaylock uses the swaylock PAM service (/etc/pam.d/swaylock).

[plum]

@kennylevinsen Ah! Thanks KIndly; I see there is no such file installed iwth the aur package manager. I shall try one of my own making to direct swaylock to the /etc/pam.d/login config file.