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 812469 - pcscd process is dead after a desktop restart.
Summary: pcscd process is dead after a desktop restart.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pcsc-lite
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bob Relyea
QA Contact: IDM QE LIST
URL:
Whiteboard:
: 808733 821008 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-13 19:54 UTC by Asha Akkiangady
Modified: 2018-11-30 22:36 UTC (History)
7 users (show)

Fixed In Version: pcsc-lite-1.5.2-7.el6
Doc Type: Bug Fix
Doc Text:
Cause The pcscd init scrip was pointing to the wrong value to identify the haldaemon. It was also starting up at run-level 2. Consequence chkconfig would not automatically place pcscd after the start of haldaemon. This would casue pcscd to fail to see usb readers (the most common readers). Fix Change the pcscd init script to properly identify haldaemon and only start at run-levels 3,4, and 5. Result chkconfig will now correctly place pcscd start after haldaemon.
Clone Of:
Environment:
Last Closed: 2012-06-20 15:14:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0990 0 normal SHIPPED_LIVE pcsc-lite bug fix update 2012-06-19 21:11:23 UTC

Description Asha Akkiangady 2012-04-13 19:54:52 UTC 
Description of problem:
pcscd process is dead after a desktop restart.

Version-Release number of selected component (if applicable):
pcsc-lite-1.5.2-6.el6.i686
coolkey-1.1.0-19.el6.i686
esc-1.1.0-24.el6_2.2.i686

How reproducible:


Steps to Reproduce:
1. Restart a Rhel 6.2 desktop when z-stream packages are installed.
  
Actual results:
pcscd process is dead.

Expected results:
pcscd should be running.

Additional info:
Smart card login requires pcscd to be running upon a desktop restart.
Comment 2 Asha Akkiangady 2012-04-13 20:04:34 UTC 
/var/log/messages has this:

Apr 13 15:58:26 dhcp231-57 pcscd: pcscdaemon.c:506:main() pcsc-lite 1.5.2 daemon ready.
Apr 13 15:58:26 dhcp231-57 acpid: starting up
Apr 13 15:58:26 dhcp231-57 acpid: 1 rule loaded
Apr 13 15:58:26 dhcp231-57 acpid: waiting for events: event logging is off
Apr 13 15:58:26 dhcp231-57 pcscd: hotplug_libhal.c:490:HPRegisterForHotplugEvents() Could not initialise connection to hald.
Apr 13 15:58:26 dhcp231-57 pcscd: hotplug_libhal.c:491:HPRegisterForHotplugEvents() Normally this means the HAL daemon (hald) is not running or not ready.
Apr 13 15:58:26 dhcp231-57 pcscd: pcscdaemon.c:525:main() SVCServiceRunLoop returned
Apr 13 15:58:26 dhcp231-57 pcscd: pcscdaemon.c:531:at_exit() cleaning /var/run
Comment 3 Bob Relyea 2012-04-14 00:24:50 UTC 
Asha, see bug 788474, comment 5 If that resolves your problem, then close this bug as a dup of that one.

If it doesn't resolve your problem you may be running into bug 808733 which looks similiar, but doesn't seem to be the same. The latter bug I can't reproduce, so I would probably like to look at your system, but that will have to wait until after next week.

bob
Comment 4 Asha Akkiangady 2012-04-16 16:11:00 UTC 
Applied the work-around (https://bugzilla.redhat.com/show_bug.cgi?id=788474#c5), after the desktop restart pcscd process fails to start.

/var/log/messages has this:

Apr 16 10:57:51 dhcp231-57 pcscd: pcscdaemon.c:506:main() pcsc-lite 1.5.2 daemon ready.
Apr 16 10:57:51 dhcp231-57 acpid: starting up
Apr 16 10:57:51 dhcp231-57 acpid: 1 rule loaded
Apr 16 10:57:51 dhcp231-57 acpid: waiting for events: event logging is off
Apr 16 10:57:51 dhcp231-57 pcscd: hotplug_libhal.c:490:HPRegisterForHotplugEvents() Could not initialise connection to hald.
Apr 16 10:57:51 dhcp231-57 pcscd: hotplug_libhal.c:491:HPRegisterForHotplugEvents() Normally this means the HAL daemon (hald) is not running or not ready.
Apr 16 10:57:51 dhcp231-57 pcscd: pcscdaemon.c:525:main() SVCServiceRunLoop returned
Apr 16 10:57:51 dhcp231-57 pcscd: pcscdaemon.c:531:at_exit() cleaning /var/run
Comment 7 Suzanne Logcher 2012-04-19 20:53:35 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.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 9 Bob Relyea 2012-04-26 21:41:55 UTC 
Asha, can you also try the following:

changeL

# Default-Start: 2 3 4 5

To

# Default-Start: 3 4 5

and

# chkconfig:   2345 25 88

to

# chkconfig:   345 25 88


then do:
/sbin/service pcscd stop
/sbin/chkconfig --del pcscd
/sbin/chkconfig --add pcscd
/sbin/service pcscd start




bob
Comment 10 Asha Akkiangady 2012-04-27 16:27:35 UTC 
With the work-around (comment 9) pcscd starts successfully when desktop is restarted.
Comment 11 Bob Relyea 2012-04-27 23:57:07 UTC 
Thanks, I'll update pcscd once this gets approved.

bob
Comment 16 Bob Relyea 2012-05-01 17:34:11 UTC 
    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:
Cause
   The pcscd init scrip was pointing to the wrong value to identify the haldaemon. It was also starting up at run-level 2.
Consequence
   chkconfig would not automatically place pcscd after the start of haldaemon. This would casue pcscd to fail to see usb readers (the most common readers).
Fix
    Change the pcscd init script to properly identify haldaemon and only start at run-levels 3,4, and 5.
Result
    chkconfig will now correctly place pcscd start after haldaemon.
Comment 17 Bob Relyea 2012-05-01 17:39:29 UTC 
*** Bug 788474 has been marked as a duplicate of this bug. ***
Comment 18 Bob Relyea 2012-05-01 17:41:54 UTC 
*** Bug 808733 has been marked as a duplicate of this bug. ***
Comment 19 Asha Akkiangady 2012-05-03 13:10:15 UTC 
Verified.

Version :: pcsc-lite-1.5.2-7.el6

pcscd process starts successfully when RHEL 6.3 desktop is boot-up.
Comment 22 Bob Relyea 2012-05-11 19:17:48 UTC 
*** Bug 821008 has been marked as a duplicate of this bug. ***
Comment 29 errata-xmlrpc 2012-06-20 15:14:27 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-2012-0990.html
Note You need to log in before you can comment on or make changes to this bug.