search

lahwaacz / sxlock

MIT License
41 stars 21 forks source link

Error opening /var/log/faillog for update #6

Closed orschiro closed 10 years ago

orschiro commented 10 years ago

I just noticed that sxlock tries to write to /var/log/faillog but fails:

~ journalctl -b _PID=5509 
-- Logs begin at Mi 2013-12-04 22:23:53 CET, end at Mi 2014-03-19 12:37:35 CET. --
Mär 19 10:28:03 thinkpad sxlock[5509]: Warning: no primary output detected, falling back to LVDS1.
Mär 19 12:11:28 thinkpad sxlock[5509]: pam_tally(login:auth): Error opening /var/log/faillog for update
Mär 19 12:11:28 thinkpad sxlock[5509]: pam_tally(login:auth): Error opening /var/log/faillog for read

Is this because I am running it as normal user? Any workaround for this or can it be safely ignored?

lahwaacz commented 10 years ago

It seems that I have been using the wrong pam file all along, this issue was reported and fixed last year for i3lock: FS#31544. Unfortunately I did not notice it when sxlock was being created (I was using i3lock back then)... Thanks for reporting.