RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When locking console in a virtual machine the vlock seems get to endless loop and print only the following message:
The pts/1 is now locked by pkis.
Authentication failure.
It is not possible to enter password at all and it continues until it is killed from another terminal.
It was tested on virtual machine only, but it is expected to work.

Version-Release number of selected component (if applicable):
kbd-1.15.5-6.el7

How reproducible:
always

Steps to Reproduce:
[pkis@rhel7 ~ ]$ vlock 

The pts/1 is now locked by pkis.
Authentication failure.


The pts/1 is now locked by pkis.
Authentication failure.

....%<...........................

From other terminal:
[root@rhel7 ~ ]# killall -9 vlock

Actual results:
It is not possible to unlock.

Expected results:
[pkis@rhel6 ~]$ vlock
 *** This tty is not a VC (virtual console). ***
 *** It may not be securely locked. ***

This TTY is now locked.
Please enter the password to unlock.
pkis's Password: 
[pkis@rhel6 ~]$

This fix appears to be incomplete - while the missing configuration file has been re-added, vlock doesn't appear to be calling pam_setcred() after successfully verifying the user's identity as the old version did (see also bug #913311).

VERIFIED on kbd-1.15.5-7.el7.x86_64
tested on tty and ssh with success on both

The problem I mentioned in comment #4 appears to be causing bug #1029374.  Does that fix belong here, or in a new bug?

Hi Nalin,
problem described in comment 1 is fixed, this blocker bug has to be verified by the end of this week.

I was unable to reproduce your bug 913311. Please try to reproduce on kbd-1.15.5-7.el7.x86_64 and then be sure to clone the bug to RHEL7 product. If I had succeeded, I would have done that.

Alright, then, cloning the other bug.  Thanks!

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.