OK, i've done further testing and my previous diagnosis isn't quite
right.  The sarge package appears to now be failing on my system at
USB device removal/insert time as well.

So i've gone back to the lenny/sid (0.6.14-1) package.  What i've
found is that upon device insertion, the openct framework appears to
fail.

but if i restart openct with the device already inserted (via
/etc/init.d/openct/restart), everything works properly until the next
removal/reinsertion.

Thoughts?  Suggestions?  My workaround at the moment is to bind an
ACPI hotkey on my machine to restart the openct framework, so i can
press that after inserting the USB device, and then (fingers-crossed)
pam-p11 authentication can continue normally.  This shouldn't be
necessary, though.

Another thing worth noting is that /var/run/openct is currently
filling up with status.lock.<pid> files.  One new file is added per
device insertion, as well as one per restart of the openct framework.
This leads me to suspect some process dying while holding a lockfile,
but i don't know openct well enough to know what other details to look
for.

Let me know how i can help resolve this,

           --dkg

Attachment: pgpYOAuCqDoqK.pgp
Description: PGP signature

Reply via email to