Bug 486403
Summary: | pcsc-lite cannot not initialise connection to hald | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Mueller <dsm42> |
Component: | pcsc-lite | Assignee: | Bob Relyea <rrelyea> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | jdy, piskozub, rrelyea |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-12-18 07:58:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Mueller
2009-02-19 16:25:55 UTC
Do me a favor, try the following change: in /etc/init.d/pcsc-lite change > chkconfig: 2345 25 88 to > chkconfig: 345 27 88 bob you man have to stop pcscd and run the following command after you made the changes: /sbin/chkconfig pcscd resetpriorities then restart pcscd. bob Tried the change and rebooted, still didn't work. The file name was actually /etc/init.d/pcscd. Looking at the order of startup in /var/log/boot.log, it looks like pcsc-lite is starting before the HAL daemon. Could this be a problem? Also, I don't know if this would make a difference, but the system was a Fedora 8 system that was updated to Fedora 10 using the anaconda installer on the Fedora 10 DVD. > Looking at the order of startup in /var/log/boot.log, it looks like pcsc-lite
> is starting before the HAL daemon. Could this be a problem?
I'm presuming that this is the problem. On my fresh install of Fedora 10 everything is started up correctly (even without the change). There is an LSB header which includes the lines 'Should start: udev hal openct'
Even though the chkconfig line has 25, on my system the daemon is start at priority 26 (making it start after hal).
what do you get if you run:
ls *hal* *pcsc*
In each of these directories:
rc2.d rc3.d rc4.d and rc5.d ?
bob
(In reply to comment #4) > what do you get if you run: > > ls *hal* *pcsc* > > In each of these directories: > > rc2.d rc3.d rc4.d and rc5.d ? # cd /etc/rc.d # ls rc*/*hal* rc0.d/K02haldaemon rc1.d/K02haldaemon rc3.d/S98haldaemon rc5.d/S98haldaemon rc0.d/S01halt rc2.d/K02haldaemon rc4.d/S98haldaemon rc6.d/K02haldaemon # ls rc*/*pcsc* rc0.d/K74pcscd rc2.d/S27pcscd rc4.d/S27pcscd rc6.d/K74pcscd rc1.d/K74pcscd rc3.d/S27pcscd rc5.d/S27pcscd Which makes the problem pretty obvious to me. Taking a hint from your previous post in comment #2, I then ran /sbin/chkconfig haldaemon resetpriorities and rebooted and things work properly. # ls rc*/*hal* rc0.d/K02haldaemon rc1.d/K02haldaemon rc3.d/S26haldaemon rc5.d/S26haldaemon rc0.d/S01halt rc2.d/K74haldaemon rc4.d/S26haldaemon rc6.d/K02haldaemon So it looks like this might have been a problem with Anaconda's update; the priority changed between Fedora releases and resetpriorities wasn't run. I had the same problem with yum update so Anaconda is most probably innocent (or at least not the only guilty party). This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Please reopen. Still a problem with FC12 as of today's updates. I have to do a service pcscd start even though the service is already running. Checking the logs, pcscd looks to be starting before hotplug_libhal.c can connect to HAL service. |