On 28/04/09 22:06, Andreas Jellinghaus wrote: > can you check which configuration the ubuntu package has? > a hal file (official suggestion), an udev rule or a hotplug map file?
It seems to use a udev rule file, /lib/udev/rules.d/40-openct.rules > 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). It runs /lib/udev/openct_usb and the file is touched. > 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. I added these lines at the top of /lib/udev/openct_usb. The log file was created but was empty. > 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). As my previous report showed, I am seeing messages from ifdhandler, but udev doesn't seem to be giving it a valid device name. -- 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