can you check which configuration the ubuntu package has? a hal file (official suggestion), an udev rule or a hotplug map file?
if so, what is the usb vendor and product id, and are those matched in that file? what script is configured to be triggered by that file? can you check if that script is run? (e.g. insert a line "touch /tmp/openct-script-is-run" and see if it created that file). if that script is run, can you try inserting these commands: exec 2> /tmp/openct-script.log 2>&1 set -x re-insert the token and if that log file is created, copy it aside and attach it later to this bug. if that script seems to work (no errors etc.) check if openct-control/ifdhandler is started by the script. you can simply increase debug level in openct.conf to 5 or 6 or so, and make sure syslog logs them (usualy does, see /var/log/messages or something like that), and check if openct is started (e.g. messages from openct-control or ifdhandler). maybe any of these actions can show us what is wrong and how we can fix it. and if anyone here knows what the magic key is to turn a patch fixing a real-world problem, into an updated package in both debian, the next ubuntu _AND_ jaunty-updates, please let us know so we can try. I failed much too often:( -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
