Hi, to debug this roblem, please show:
- the version of your linux kernel. some older 2.6.22 or so were buggy.
- lsusb - what vendor id and product id does the etoken use
- setup - no idea what ubuntu currently uses? and packages.ubuntu.com isn't
working for me.
does openct come with udev rules file or an fdi file for hal?
- is that vendor id and product id listed in the udev rules / hal fdi file?
- if the problem is udev related, udevmonitor (--env and --kernel --env)
output while a token is plugged in might help.
- the script executed by udev or hal: can you edit it and put something like
this in it:
exec >> /root/openct-debug.log 2>&1
echo
date
echo $0: $*
export
set +x
then have a look what is in /root/openct-debug.log.
if device names like /dev/bus/usb/003/004 or similar show up,
please add an appropriate "ls -l $DEVNAME" (or what the relevant variable is)
to the script.
maybe the file gets only created after openct tries to use it or a similar race
condition.
oh, I forgot to mention: increasing debug level in openct.conf and looking in
syslog for "ifdhandler"
syslog messages is also a good idea.
sorry, I haven't debugged openct in a while and lost the track of the latest
status. the bug you mentioned
looks like it was finally working.
I'm currently quite busy, won't have much time for this, but still I will try
to help to track down the issue
and fix it.
Regards, Andreas
--
openct doesn't recognize etoken
https://bugs.launchpad.net/bugs/246392
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
