I had a system that was not updated for ~4 months. After upgrading all the packages, I couldn't unlock a terminal in which I ran vlock before the upgrade. Going to another tty and running vlock works just fine and can be unlocked normally. Vlock replies [user]'s Vlock: Module is unknown root's Vlock: Module is unknown and then goes back to locked state without asking for a password. I've tried to figure out a way to replicate this behaviour but I'm not sure how to do that. I suppose the problem is in the vlock upgrade, but I've upgraded almost 200 packages with it, so I can't be totally sure that is the problem. Reproducible: Didn't try Steps to Reproduce: 1. Use vlock in a tty 2. Go to a second tty and update 3. Try to unlock the first tty Actual Results: The tty can't be unlocked ([user]'s Vlock: Module is unknown) Expected Results: Vlock should ask for a password, and the terminal should unlock if the password is correct. There were no other programs running when this happened.
please provide "emerge --info vlock" output
Created attachment 408416 [details] emerge --info vlock Output from emerge --info vlock
Added as an attachment. I'm not sure it'll help now tho, the program is working as it should. This behaviour only happens in a tty that was locked before the upgrade.
this is almost certainly due to a recent pam upgrade. you need to restart all programs using pam.
please attach the full build log
Hi I haven't been able to reproduce this issue. Meanwhile, I've bumped the ebuild to EAPI version 6 and updated HOMEPAGE as well as SRC_URI (it points to github now). Taking shell-tools@ off of CC.
I can neither reproduce, also, indeed, you need to restart programs using pam after the update
