Source: libfprint Version: 1:1.94.9-1 Severity: normal Hi,
I just installed a package unrelated to libfprint but then my installation got stuck for more than five minutes at trying to set up libfprint. Looking at htop I saw the postinst script being busy calling "udevadm trigger". This operation did not cause CPU nor I/O load on my system but it still took several minutes to go through the list of devices. Could this be sped up somehow? Could udevadm not be called in parallel instead of in series? Or could at the very least not something be printed on stderr like "This can take a very long time"? Thanks! cheers, josch
