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
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jerome Leclanche (Adys)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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!
Comment by Ivy Foster (escondida) - Thursday, 10 October 2019, 21:57 GMT
zreeon, does this still occur for you?
Comment by Daenney (daenney) - Thursday, 02 January 2020, 18:16 GMT
This bug still occurs, and appears to be the same thing as https://bugs.archlinux.org/task/31544 (i3lock issue). The problem is that the PAM configuration shipped by upstream doesn't work for Arch. The change required can be found in i3lock''s pkgbuild: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/i3lock#n24
Comment by Daenney (daenney) - Thursday, 02 January 2020, 18:37 GMT
It turns out, it might just be an outdated PAM config, and no changes to the config swaylock ships may be required. I took a further look, and I noticed a system-login.pacnew (which gets included by login through system-local-login) which moved from pam_tally to pam_tally2. Putting the new config in place resolved the issue.

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.
Comment by Michaël Defferrard (mdeff) - Saturday, 04 January 2020, 17:55 GMT
I confirm that the move to tally2 suppresses those errors.

Upstream discussion: https://github.com/swaywm/swaylock/issues/27

Loading...