FS#53358 - [sway] swaylock can't access /var/log/faillog
Attached to Project:
Community Packages
Opened by Alex (zreeon) - Saturday, 18 March 2017, 09:33 GMT
Last edited by Brett Cornwall (ainola) - Saturday, 04 April 2020, 21:11 GMT
Opened by Alex (zreeon) - Saturday, 18 March 2017, 09:33 GMT
Last edited by Brett Cornwall (ainola) - Saturday, 04 April 2020, 21:11 GMT
|
Details
Description:
After running swaylock, journalctl reports: pam_tally(swaylock:auth): Error opening /var/log/faillog for read pam_tally(swaylock:auth): Error opening /var/log/faillog for update This may be related to a bug that i3lock experienced: https://bugs.archlinux.org/task/31544 Additional info: * sway 0.12.1 Steps to reproduce: `swaylock` `journalctl -p 1..0` |
This task depends upon
Closed by Brett Cornwall (ainola)
Saturday, 04 April 2020, 21:11 GMT
Reason for closing: Works for me
Additional comments about closing: Considering the OP mentioned that the move to pam_tally2 solved the issue and was confirmed by another suggests this is no longer an issue.
I am unable to replicate on my machine and can only assume that this is fixed. Thanks for the report!
Saturday, 04 April 2020, 21:11 GMT
Reason for closing: Works for me
Additional comments about closing: Considering the OP mentioned that the move to pam_tally2 solved the issue and was confirmed by another suggests this is no longer an issue.
I am unable to replicate on my machine and can only assume that this is fixed. Thanks for the report!
This change happened on https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/pambase&id=63d98c5eca79ea60493241951f6aeb5c98c9b892, 1st of January 2019. so this error probably only manifests on systems that were installed earlier and whose administrators missed the notice during the upgrade.
Upstream discussion: https://github.com/swaywm/swaylock/issues/27