Comment 5 for bug 2066218

I feel this is because the device is not in the libfprint list of unsupported devices, for which we still apply the auto-suspend mode.

The device is now added to https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-Devices and so once we sync that doc with the libfprint code, it will not leak anymore even if the driver is not installed.

Let me know if that's something else, but if that's the case then it's only about fixing libfprint to generate an udev/hwdb rule for that.