Bug 812469
| Summary: | pcscd process is dead after a desktop restart. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Asha Akkiangady <aakkiang> |
| Component: | pcsc-lite | Assignee: | Bob Relyea <rrelyea> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | jgalipea, ludovic.rousseau, mniranja, nkinder, o.h.weiergraeber, prutledg, syeghiay |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-20 15:14:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Asha Akkiangady
2012-04-13 19:54:52 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 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 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 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. 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 With the work-around (comment 9) pcscd starts successfully when desktop is restarted. Thanks, I'll update pcscd once this gets approved. bob
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.
*** Bug 788474 has been marked as a duplicate of this bug. *** *** Bug 808733 has been marked as a duplicate of this bug. *** Verified. Version :: pcsc-lite-1.5.2-7.el6 pcscd process starts successfully when RHEL 6.3 desktop is boot-up. *** Bug 821008 has been marked as a duplicate of this bug. *** 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 |