This bug has been copied from bug #654896 and has been proposed to be backported to 5.5 z-stream (EUS).
Unlocking a locked screen when logged in with a smart card with gnome-screensaver-2.16.1-8.el5_5.2 on a Rhel 5.5 host works fine. Tested following scenarios: 1. Authentication configured to Use smart card: ON Enforce smart card: OFF Log out behaviour configured to: Ignore. Login to the desktop with a smart card. Manually lock the screen by selecting menu item 'Lock Screen'. Mouse move prompts to enter password. Correct smart card pin unlocks the screen. 2. Authentication configured to Use smart card: ON Enforce smart card: OFF Log out behaviour configured to: Lock. Login to the desktop with a smart card. Remove the smart card from the hook. Screen gets locked. Re-insert the smart card. Correct smart card pin unlocks the screen. 3. Authentication configured to Use smart card: ON Enforce smart card: ON Log out behaviour configured to: Ignore. Login to the desktop with a smart card. Manually lock the screen by selecting menu item 'Lock Screen'. Mouse move prompts to enter password. Correct smart card pin unlocks the screen. 4. Authentication configured to Use smart card: ON Enforce smart card: ON Log out behaviour configured to: Lock. Login to the desktop with a smart card. Remove the smart card from the hook. Screen gets locked. Re-insert the smart card. Correct smart card pin unlocks the screen. 5. Authentication configured to Use smart card: ON Enforce smart card: OFF Log out behaviour configured to: Lock. Login to the desktop with a smart card. Screen gets locked due to inactivity. Move the mouse. Correct smart card pin unlocks the screen. Marking the bug verified.
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 using cached credentials with the System Security Services Daemon (SSSD), an attempt to unlock a locked screen in the "offline mode" could fail. With this update, this error has been fixed, and such attempt no longer fails.
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-0944.html