Hi there! On Sun, 05 Aug 2012 16:17:02 +0200, Andrew Pimlott wrote: > Excerpts from Didier Raboud's message of Sun Aug 05 02:33:45 -0700 2012: >> Le samedi, 4 août 2012 23.56:02, Andrew Pimlott a écrit : >> > libfprint0 should trigger the udev rules when it installs them. >> >> I don't think that libfprint should be special-cased here. On my system, >> there >> are 32 different packages installing udev rules under /lib/udev/rules.d and >> libfprint is certainly not the only one that would benefit from "udevadm >> trigger" runs. > > That sound reasonable. I would definitely be happy with a solution > that covers other packages. The only thing that might be different is > that most other devices you can simply remove and plug in again. I > can't do that with my build-in fingerprint reader.
IMHO this is enough for libfprint being a special case. >> In my understanding of the situation of the udev rules, there is a >> requirement >> to reboot to have things working correctly; and that's nothing libfprint >> should fix for its own benefit. > > That doesn't sound reasonable to me! I'm not used to rebooting after I > install packages, even if they are desktop-oriented. Not reasonable to me either and `man udevadm` does not say anything about reboot. Marco, do you have any suggestion? Thx, bye, Gismo / Luca
pgpArlykLQ2fs.pgp
Description: PGP signature
