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 662651 - Can't unlock if card is not inserted when movin mouse.
Summary: Can't unlock if card is not inserted when movin mouse.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-screensaver
Version: 6.0
Hardware: x86_64
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1002711
TreeView+ depends on / blocked
 
Reported: 2010-12-13 14:12 UTC by Patrik Martinsson
Modified: 2019-03-22 07:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-18 13:53:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screencast of the problem and screensaver debuglog. (756.86 KB, application/x-gzip)
2010-12-13 14:12 UTC, Patrik Martinsson 		no flags Details
View All

Description Patrik Martinsson 2010-12-13 14:12:32 UTC 
Created attachment 468381 [details]
Screencast of the problem and screensaver debuglog.

Description of problem:
If you use pcks11-token to login and have activated "Card Removal Action" in the authentication confuration, you can't unlock the screen if you first move the mouse and then insert your card. 

How reproducible:
Always, if mouse is moved before insertion of card.

Steps to Reproduce:
1. Remove card, let the screen lock.
2. Move the mouse the poke the screensaver. 
3. Insert card and enter pin. 
  
Actual results:
*** stack smashing detected ***: /usr/libexec/gnome-screensaver-dialog terminated.

Expected results:
Gnome-screensaver unlocks. 


Additional info:

cat /etc/pam.d/gnome-screensaver 
-------------------
auth     [success=done ignore=ignore default=bad] pam_selinux_permit.so

session    include	system-auth
auth       include	system-auth
auth       optional     pam_gnome_keyring.so
account    include	system-auth
password   include	system-auth
-------------------

cat /etc/pam.d/gnome-screensaver (auth part)
-------------------
auth        required      pam_env.so
auth        [success=1 default=ignore] pam_succeed_if.so service notin login:gdm:xdm:kdm:xscreensaver:gnome-screensaver:kscreensaver quiet use_uid
auth        [default=die ignore=ignore success=ok] pam_pkcs11.so wait_for_card 
-------------------

tail -f /var/log/secure  
-------------------
Card is removed and I'm moving the mouse, 
Dec 13 14:59:53 nrlx099 gnome-screensaver-dialog: pam_pkcs11(gnome-screensaver:auth): no suitable token available
Dec 13 14:59:53 nrlx099 gnome-screensaver-dialog: pam_pkcs11(gnome-screensaver:auth): conversation failed

I'm now inserting the card,
Dec 13 15:00:04 nrlx099 gnome-screensaver-dialog: pam_pkcs11(gnome-screensaver:auth): conversation failed

Entering pin, nothing shows in the log, however now the 
*** stack smashing detected ***: /usr/libexec/gnome-screensaver-dialog terminated shows up in the terminal running gnome-screensaver in debug mode.

Entering pin again, screen unlocks but following is seen in /var/log/secure
Dec 13 15:00:19 nrlx099 gnome-screensaver-dialog: pam_pkcs11(gnome-screensaver:auth): conversation failed
Dec 13 15:00:19 nrlx099 gnome-screensaver-dialog: pam_pkcs11(gnome-screensaver:auth): conversation failed
-------------------


I've attached the logoutput from the gnome-screensaver debug terminal and a small screencast of the procedure so it makes sence to everyone.

Please tell me if there is anything more i need to attach, I would love to see this fixed, we hade the same problem back in Fedora 10.
Comment 2 RHEL Program Management 2011-01-07 15:52:39 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 Chris Williams 2015-09-18 13:53:07 UTC 
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.
Note You need to log in before you can comment on or make changes to this bug.