Bug 556616

Summary:	app-misc/vlock: can't be unlocked after an upgrade
Product:	Gentoo Linux	Reporter:	Yuri Numerov <achi>
Component:	Current packages	Assignee:	PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled>
Status:	RESOLVED TEST-REQUEST
Severity:	minor	CC:	achi, alex_y_xu
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info vlock

Description Yuri Numerov 2015-08-04 02:49:30 UTC

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.

Comment 1 Pacho Ramos gentoo-dev

2015-08-06 13:36:24 UTC

please provide "emerge --info vlock" output

Comment 2 Yuri Numerov 2015-08-06 15:43:21 UTC

Created attachment 408416 [details]
emerge --info vlock

Output from emerge --info vlock

Comment 3 Yuri Numerov 2015-08-06 15:44:56 UTC

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.

Comment 4 Alex Xu (Hello71) 2015-08-13 00:02:30 UTC

this is almost certainly due to a recent pam upgrade. you need to restart all programs using pam.

Comment 5 SpanKY gentoo-dev

2015-08-13 02:30:21 UTC

please attach the full build log

Comment 6 Patrice Clement (RETIRED) gentoo-dev

2017-08-03 19:53:16 UTC

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.

Comment 7 Pacho Ramos gentoo-dev

2018-09-24 13:30:33 UTC

I can neither reproduce, also, indeed, you need to restart programs using pam after the update