Bug 708430

Summary: When resetting password, any errors from previous password attemps still show
Product: Red Hat Enterprise Linux 6 Reporter: Matthew Mosesohn <mmosesoh>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: msanders, tpelka
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: Environment:
Last Closed: 2011-12-06 17:58:02 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: 637248    
Attachments:
Description Flags
photograph of screen displaying the error at step 8 none

Description Matthew Mosesohn 2011-05-27 15:54:48 UTC 
Description of problem:
If you try to change your password via GDM with an expired password, and fail to change it the first time, the error shown is still present when typing it the second try.  This confuses a user who is trying to reset his or her password.

Version-Release number of selected component (if applicable):
gdm-2.30.4-21.el6_0.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. as root: useradd testuser
2. passwd testuser  (input changeme as password)
3. switch to GDM login
4. enter testuser as username
5. enter changeme as password
6. You will be prompted to repeat old password
7. Type new password: abc   (it's too short for the password policy)
8. Type new password that is strong such as ">8rN5tLnu" 
Actual results:
When typing this new password and repeating it, the error from the previous password is still visible.

Expected results:
The previous error should be dismissed when repeating password.


Additional info:
Comment 1 Matthew Mosesohn 2011-05-27 15:55:21 UTC 
Created attachment 501333 [details]
photograph of screen displaying the error at step 8
Comment 4 Ray Strode [halfline] 2011-06-20 15:00:16 UTC 
It doesn't disappear after 2 seconds?

We have a better message queueing mechanism in git we could backport.

devack+
Comment 10 errata-xmlrpc 2011-12-06 17:58:02 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