we had problems like this before: the kernel finds out there is a new
usb device. udev gets an event. udev manages both to tell openct
about it and create a file in /dev/ somewhere. but again the communication
is flawed somehow, openct is not told what that new device file is. sad.
lets switch to hal setup, as the udev developers themself tell us to do,
and they don't want programs like openct to use udev directly it seems.
hald setup on the other side is tested and supported, so that seems to
be the better choice.
thanks to a huge amount of work by Stanislav Brabec from suse, openct
has even much better hal setup now, and I created a pre-release from svn
trunk and packaged it for ubuntu, and it works on my machine. can you
give it a try?
http://www.opensc-project.org/debian/openct/
has the source and diff.gz and amd64 binaries.
if it works I will release openct 0.6.16 soon and hope that both debian and
ubuntu can pick it up to close bugs (or backport the fixes if they prefer that).
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
