The pcscd init script says it wants to be started at priority 25, the hal init script says 26. However pcscd refuses to start up if hal is not around. Hence the order is wrong: hal needs to be started before pcscd. # sudo rpm -qf /etc/init.d/haldaemon /etc/init.d/pcscd hal-0.5.14-3.fc13.x86_64 pcsc-lite-1.5.5-3.fc13.x86_64
Of course, this completely breaks the entire package.
As far as I know, chkconfig is smart enough to recalculate priorities so that the service gets started later than the ones mentioned in Required-Start and Should-Start tags in LSB header. An earlier bug #565241 was about referencing invalid init script names in LSB header. Now that this is fixed and pcscd init script correctly references haldaemon, a simple "chkconfig pcscd resetpriorities" should fix the order. I was lucky enough to get my hands on a clean Fedora 13 Beta installation today and pcscd was indeed started on priority 27 (even thought there is priority 25 in chkconfig: line). However, to be on a safe side I've applied a patch to also explicitly fix chkconfig priorities. Please test pcsc-lite-1.5.5-4.fc13 and give karma if the init script order is now fixed for you. (Note that you still need to run "chkconfig pcscd resetpriorities" after updating for the changes to take effect. This is also a recommended step in Fedora yum upgrade faq.) Thanks for reporting this!
pcsc-lite-1.5.5-4.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/pcsc-lite-1.5.5-4.fc13
pcsc-lite-1.5.5-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pcsc-lite'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pcsc-lite-1.5.5-4.fc13
pcsc-lite-1.5.5-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.