Bug 679081

Summary:	PAM messages get cleared after incorrect password attempt
Product:	Red Hat Enterprise Linux 5	Reporter:	Jiri Koten <jkoten>
Component:	gnome-screensaver	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WONTFIX	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.6	CC:	jkoten, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-25 21:03:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jiri Koten 2011-02-21 14:30:28 UTC

Description of problem:
Normally when you enter bad password, gnome-screensaver displays msg "Incorrect password" for a short time and then "reset" the prompt dialog. (i.e.,msg about wrong passwd disappears). 
The problem occurs when there is some pam msg displayed on passwd prompt and you enter bad passwd. The msg "Incorrect password" is not displayed and prompt doesn't reset itself properly, i.e. the pam msg which should be displayed on prompt gets cleared. 

Version-Release number of selected component (if applicable):
gnome-screensaver-2.16.1-8.el5_6.3

How reproducible:
100%

Steps to Reproduce:
1. add "auth optional pam_echo.so file=/tmp/somefilewithashortmessageinit" to the top of /etc/pam.d/system-auth
2. Activate Lock screen
3. Try to unlock screen with bad password
  
Actual results:
The msg "Incorrect password" is not displayed, pam message from Step 1 gets cleared.

Expected results:
Prompt shows briefly msg "Incorrect password" and then pam message from Step 1 is displayed again.

Comment 1 RHEL Program Management 2014-03-07 12:51:28 UTC

This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 Ondrej Vasik 2014-06-25 21:03:43 UTC

I take it as no need to escalate - as this doesn't qualify for production phase 3, closing WONTFIX for RHEL 5, thanks for reply.