You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cinnamon-screensaver-pam-helper should immediately cancel the authentication and exit on receiving SIGTERM. But it seems to authenticate once more with empty input which must fail (see the log below).
Actually I'm encountering with #412 that my account will be locked randomly. After digging into source code I figured out every entry in faillock's log corresponds to a call on AuthClient.cancel, which send SIGTERM to pamhelper.
USER:
When Type Source Valid
2024-01-18 14:57:35 TTY :0 V
To reproduce the original issue: Move your mouse or sth like that to enter UnlockDialog and then press ESC or wait 30 sec (timeout) to exit. You will find an added entry in faillock.
Expected behavior
pamhelper should exit immediately and do no extra work on SIGTERM. Actually if kill it with SIGINT etc you can bypass sigterm handler and let it work as expected (?)
Additional information
No response
The text was updated successfully, but these errors were encountered:
Distribution
Arch Linux
Package version
6.0.2
Graphics hardware in use
No response
Frequency
Always
Bug description
cinnamon-screensaver-pam-helper
should immediately cancel the authentication and exit on receiving SIGTERM. But it seems to authenticate once more with empty input which must fail (see the log below).Actually I'm encountering with #412 that my account will be locked randomly. After digging into source code I figured out every entry in
faillock
's log corresponds to a call onAuthClient.cancel
, which send SIGTERM to pamhelper.Steps to reproduce
Run pamhelper:
In another terminal, send SIGTERM to it:
And log of pamhelper after that:
Check
faillock
:To reproduce the original issue: Move your mouse or sth like that to enter
UnlockDialog
and then press ESC or wait 30 sec (timeout) to exit. You will find an added entry infaillock
.Expected behavior
pamhelper should exit immediately and do no extra work on SIGTERM. Actually if kill it with SIGINT etc you can bypass sigterm handler and let it work as expected (?)
Additional information
No response
The text was updated successfully, but these errors were encountered: