All my USB devices are autosuspending now because of a too broad rule in libfprint

Bug #1906296 reported by Iain Lane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libfprint (Ubuntu)
Fix Released
High
Marco Trevisan (Treviño)

Bug Description

laney@raleigh> apt policy libfprint-2-2
libfprint-2-2:
  Installed: 1:1.90.3+tod1-0ubuntu2
  Candidate: 1:1.90.3+tod1-0ubuntu2
  Version table:
 *** 1:1.90.3+tod1-0ubuntu2 500
        500 file:/srv/mirrors/ubuntu hirsute/main amd64 Packages
        100 /var/lib/dpkg/status

This is the USB controller on my desktop (no fingerprint reader)

laney@raleigh> sudo udevadm info /sys/devices/pci0000:00/0000:00:1d.0/usb2/
P: /devices/pci0000:00/0000:00:1d.0/usb2
N: bus/usb/002/001
L: 0
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/usb2
E: DEVNAME=/dev/bus/usb/002/001
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=1d6b/2/508
E: TYPE=9/0/0
E: BUSNUM=002
E: DEVNUM=001
E: MAJOR=189
E: MINOR=128
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=1086603
E: ID_VENDOR=Linux_5.8.0-26-generic_ehci_hcd
E: ID_VENDOR_ENC=Linux\x205.8.0-26-generic\x20ehci_hcd
E: ID_VENDOR_ID=1d6b
E: ID_MODEL=EHCI_Host_Controller
E: ID_MODEL_ENC=EHCI\x20Host\x20Controller
E: ID_MODEL_ID=0002
E: ID_REVISION=0508
E: ID_SERIAL=Linux_5.8.0-26-generic_ehci_hcd_EHCI_Host_Controller_0000:00:1d.0
E: ID_SERIAL_SHORT=0000:00:1d.0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:090000:
E: ID_VENDOR_FROM_DATABASE=Linux Foundation
E: ID_AUTOSUSPEND=1
E: ID_MODEL_FROM_DATABASE=2.0 root hub
E: ID_PATH=pci-0000:00:1d.0
E: ID_PATH_TAG=pci-0000_00_1d_0
E: LIBFPRINT_DRIVER=Hardcoded whitelist
E: ID_FOR_SEAT=usb-pci-0000_00_1d_0
E: TAGS=:snap_arduino_arduino:seat:

Note that it has

E: LIBFPRINT_DRIVER=Hardcoded whitelist

which is suspicious, why is libfprint touching that?

Furthermore, all devices attached to it have

    ATTRS{power/control}=="auto"

in particular this causes problems for my mouse which doesn't like being suspended - it takes a few seconds to wake up each time after I stop using it, which is surprisingly annoying.

It's these rules:

SUBSYSTEM=="usb", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0002", ATTRS{dev}=="*", TEST=="power/control", ATTR{power/control}="auto", MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d6b", ATTRS{idProduct}=="0002", ENV{LIBFPRINT_DRIVER}="Hardcoded whitelist"

which are matching, and they shouldn't be here since they aren't matching a fingerprint reader.

This is listed on https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported%20Devices as being "Mantra MFS100", which seems wrong I think.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libfprint-2-2 1:1.90.3+tod1-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu53
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Mon Nov 30 18:43:42 2020
InstallationDate: Installed on 2012-10-07 (2976 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
SourcePackage: libfprint
UpgradeStatus: Upgraded to hirsute on 2020-08-18 (104 days ago)

Revision history for this message
Iain Lane (laney) wrote :
Changed in libfprint (Ubuntu):
importance: Undecided → High
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
status: New → Triaged
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu3

---------------
libfprint (1:1.90.3+tod1-0ubuntu3) hirsute; urgency=medium

  * debian/patches:
    - Reorder to give upstream more priority
    - Don't use power-save mode for USB controller (LP: #1906296)

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 30 Nov 2020 20:24:59 +0100

Changed in libfprint (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.