search

SuperPrower / i3lock-fancier

Yet another i3lock fork. Now with configuration file!
Other
60 stars 7 forks source link

pam_tally(i3lock:auth) error #15

Open VGrol opened 6 years ago

VGrol commented 6 years ago

Greetings,

I3lock-fancier still calls the depreciated pam_tally which results in a log of errors in the log upon a failed login attempt.

Jul 11 16:44:15 i3lock[6740]: pam_tally(i3lock:auth): Error opening /var/log/faillog for update Jul 11 16:44:15 i3lock[6740]: pam_tally(i3lock:auth): Error opening /var/log/faillog for read Jul 11 16:44:15 i3lock[6740]: pam_tally(i3lock:setcred): Error opening /var/log/faillog for update Jul 11 16:44:15 i3lock[6740]: pam_tally(i3lock:setcred): Error opening /var/log/faillog for update

Would it be possible to migrate away from Pam_Tally? It has been depreciated for a while and was throwing some errors in the older I3 locks, I3 fancier has yet to incorporate these fixes though.

Any failed auth wants to be written to /var/log/faillog but fails as pam_tally lacks the permissions to do so. The source contains a number or potential fixes.

Source

SuperPrower commented 6 years ago

Sorry, changes I made to create i3lock-fancier were mostly made on intuition level / merged from other people's works. I tried changing main stuff to be up to date with original i3lock, but I never really was able to do that. I also still don't quite understand how to properly use pam, so I can't just fix this stuff yet.

I'll try to look into this issue, but just don't expect me to create fix and/or update anytime soon. Sorry again.