This bug has been copied from bug #606845 and has been proposed to be backported to 5.5 z-stream (EUS).
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When unlocking the screen, clicking the "Cancel" button may have caused the following message to appear in the /var/log/secure log: gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): auth could not identify password for [user] This was due to authentication dialog attempting to log in, even though no such action was requested. With this update, this error has been fixed, and clicking "Cancel" no longer attempts to authenticate a user.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,5 +1,5 @@ -When unlocking the screen, clicking the "Cancel" button may have caused the following message to appear in the /var/log/secure log: gnome-screensaver-dialog: +When unlocking the screen, clicking the "Cancel" button may have caused the following message to appear in the /var/log/secure log: - pam_unix(gnome-screensaver:auth): auth could not identify password for [user] + gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): auth could not identify password for [user] This was due to authentication dialog attempting to log in, even though no such action was requested. With this update, this error has been fixed, and clicking "Cancel" no longer attempts to authenticate a user.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0826.html