Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionPatrick Rutledge
2012-05-11 14:41:58 UTC
Description of problem:
pcscd crashes shortly after starting with a green state during boot because it relies on haldaemon to be running. after rebooting the system, pcscd will no longer start up unless manually restarted at the command line, it will not come back up after reboot. In /etc/init.d/pcscd it specifically states Should-start hal, but in rc3 and rc5, pcscd is S25 and hal is S26, which is the root cause of the bug. Manually changing pcscd to S27 fixes the problem, but this bug needs to be reviewed and fixed.
Version-Release number of selected component (if applicable):
pcsc-lite 1.5.2 el6
How reproducible:
Enable pcscd, configure a smart card, reboot system. PCSCD will not be running after system has fully rebooted.
Steps to Reproduce:
1.Configure smartcard and test authentication
2.Make sure pcscd is chkconfiged on
3.Reboot
4.service pcscd status will return not running and stale lock
Actual results:
<before reboot>
[root@smartcardtest Desktop]# service pcscd status
pcscd (pid 25701) is running...
<after reboot>
[root@smartcardtest Desktop]# service pcscd status
pcscd dead but subsys locked
[root@smartcardtest Desktop]# service pcscd restart
Stopping PC/SC smart card daemon (pcscd): [FAILED]
Starting PC/SC smart card daemon (pcscd): [ OK ]
[root@smartcardtest Desktop]# service pcscd status
pcscd (pid 2970) is running...
[root@smartcardtest Desktop]#
Expected results:
pcscd running
Additional info: