openct doesn't recognize etoken

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

IMHO there is a mistake in udev rules file named 50-openct.rules:

# eToken
ENV{MODALIAS}=="usb:v0529p050C*", RUN+="/lib/udev/openct_usb"
ENV{MODALIAS}=="usb:v0529p0514", RUN+="/lib/udev/openct_usb"
                                                             ^ there must be asterisk, as in first line

when i fix this and call udevcontrol --reload_rules, openct recognize my etoken after plugging in

sorry for buggy formatting, asterisk must be placed after "usb:v0529p0514

thanks for finding the problem.
this is an upstream problem, it was fixed in svn revision 1063 in trunk.

not sure when anyone finds time to create a new openct upstream release,
so could someone please fix this trivial issue in ubuntu packages directly?

Thanks, Andreas

I confirm this problem, a simple typo in etc/openct.udev.modalis.in.
please fix it in a new revision of the openct package.

Confirmed. The asterisk fixes it for me too. Thanks for your help guys.

This bug still is not fixed in Jaunty. Is there some reason? Also another bit is now broken: the script that the udev rules file calls, /lib/udev/openct_usb is trying to call "udevinfo" which no longer exists. It should be using "udevadm info" instead. This too is fixed in the upstream. Can we get an update in the package please?

This bug was fixed in the package openct - 0.6.19-1ubuntu1

---------------
openct (0.6.19-1ubuntu1) lucid; urgency=low

  * Fake merge from debian unstable (LP: #519713)
  * Patch for merge from hal to udev: (LP: #503119) (LP: #436545)
    (Taken from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563755)
    + Changed files:
      - debian/openct.install
      - debian/rules
  * debian/patches/init-script.patch:
    - fix directory creation in init script (LP: #131075)
  * Already fixed bugs, but not closed in LP:
    + "no appropriate entry in fdi file" (LP: #435138)
    + "Openct needs to be restarted when inserting an eToken" (LP: #368683)
    + "openct doesn't recognize etoken" (LP: #246392)
 -- Stephan Hermann <email address hidden> Wed, 10 Feb 2010 10:52:34 +0000