pcscd no longer starts on Lucid
Bug #506908 reported by
Torsten Spindler
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcsc-lite (Ubuntu) |
Fix Released
|
Medium
|
Reinhard Tartler | ||
Bug Description
As HAL is no longer started during boot time in Lucid, pcscd seems to no longer start:
Feb 22 14:34:15 wm0828 pcscd: hotplug_
Feb 22 14:34:15 wm0828 pcscd: hotplug_
Feb 22 14:34:15 wm0828 pcscd: pcscdaemon.
This is fixable by using the --without-hal compile option for pcscd.
Independent of the HAL problem an upstart job for pcscd has been provided in this bug report. This might be needed for better integration with the upstart driven gdm.
Changed in pcsc-lite (Ubuntu): | |
assignee: | Stephan Hermann (shermann) → nobody |
Changed in pcsc-lite (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- Upstart job for pcscd + pcscd no longer starts on Lucid |
description: | updated |
description: | updated |
description: | updated |
Changed in pcsc-lite (Ubuntu): | |
assignee: | nobody → Reinhard Tartler (siretart) |
To post a comment you must log in.
If pcscd should handle PCMCIA-based SmartcardReader it is necessary that pcmcia is ready and has found all devices before pcscd is started. After Start of pcscd it needs some time to initialize itself (finding all smartcardreaders, etc.).
Other resources like GDM (Smartcard-based login) and NetworkManager (Smartcard-based VPN) should wait for pcscd to be ready (if it is installed)!
As a starting point I've written an upstart init script (attached). This script emits a signal after pcscd has been started and settled down (sleep 5). I know this is ugly, but as stated before simply starting pcscd -- and after that the NetworkManager/GDM -- can lead to a kind of "race condition".
I've also changed the upstart init script for NetworkManager and GDM to wait for the emited signal.