I believe there is no real patch for specifically this problem as trigger based hardware scan should work for a long time now. Simply set hardwareScanInterval=0 in the config file and add a udev trigger script (like the one from Debian) and you're done. The introduction of the udev trigger script in the Debian package was in SVN commit r944: http://svn.debian.org/viewsvn/aqbanking?view=rev&revision=944 (but beware: possibly not complete).
With opening the bug task for Jaunty I tried to get more attention for this bug in the hope to get a fix in the package before the release of Jaunty. However I have to admit that I don't know Ubuntu's release process in detail. So please apologize for any clueless assumptions made before.... -- chipcardd4 uses lots of cpu https://bugs.launchpad.net/bugs/277412 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
