Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 661618

Summary: gdm does not pause, when printing multiple pam messages
Product: Red Hat Enterprise Linux 6 Reporter: ritz <rkhadgar>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0CC: jwest, rstrode, tpelka, vhumpa
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdm-2.30.4-32.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 785775 (view as bug list) Environment:
Last Closed: 2011-12-06 17:57:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 785775    

Description ritz 2010-12-09 08:40:27 UTC
Description of problem:
gdm does not pause, when printing multiple pam messages. Consequently, only the last message is seen. 

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. echo "no go" > /etc/nologin
2. Try to login

  
Actual results:
Only "Authentication failure" is seen

Expected results:
"no go" should be seen for atleast 2s, followed by "Authentication failure"

Comment 1 Ray Strode [halfline] 2010-12-13 17:18:04 UTC
I've worked with ritz on this bug in detail. shouldn't be too hard to get working. devack+

Comment 2 Ray Strode [halfline] 2010-12-13 21:26:36 UTC
After talking to Owen, it looks like we're going to try to push this out to 6.2

Comment 5 Ray Strode [halfline] 2011-06-28 13:19:14 UTC
this has since landed upstream (in a slightly different from), pretty sure gdm is already on the approved components list, etc.

devack+

Comment 6 RHEL Program Management 2011-06-28 13:20:53 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 9 Vitezslav Humpa 2011-08-26 14:09:34 UTC
Looks like the fix is not working, at least for the 'echo "no go" > /etc/nologin' approach with gdm-2.30.4-31.el6.

Comment 10 Ray Strode [halfline] 2011-08-26 18:41:07 UTC
indeed.  I recently changed my workflow for patchset generation and ended up getting the wrong final commit in the patchset, so it was missing one hunk.

didn't notice it locally because i was building locally with the correct patchset.

building now, gdm-2.30.4-32.el6

Comment 12 Vitezslav Humpa 2011-08-30 12:33:46 UTC
It's all good now with gdm-2.30.4-32.el6

Comment 13 errata-xmlrpc 2011-12-06 17:57:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1721.html