Bug 1339238
| Summary: | No support for the Validity Sensors, Inc. Fingerprint Reader (138a:0017) on Thinkpad T440s | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Matěj Cepl <mcepl> | ||||
| Component: | libfprint | Assignee: | Bastien Nocera <bnocera> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.3 | CC: | bxue, mclasen, tpelka | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-06-08 14:19:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1327495 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
http://thread.gmane.org/gmane.linux.fprint/2509 seems to indicate that it could be at least somehow supported, and https://launchpad.net/~fingerprint claims it is supported by the fingerprint project. Actually, with kernel 3.10.0-445.el7.x86_64, fprintd-0.5.0-4.0.el7_0.x86_64, and fprintd-pam-0.5.0-4.0.el7_0.x86_64, I get this even more confusing scenario: matej@mitmanek: ~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 Enrolling right index finger. Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-stage-passed Enroll result: enroll-completed matej@mitmanek: ~$ fprintd-list matej found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 Fingerprints for user matej on Validity VFS5011 (swipe): - #0: right-index-finger matej@mitmanek: ~$ fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify result: verify-no-match (done) matej@mitmanek: ~$ fprintd-delete matej found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 Fingerprints deleted on Validity VFS5011 matej@mitmanek: ~$ And the same goes for the GUI verification (my finger can be enrolled, but not verified). (In reply to Matěj Cepl from comment #3) > Actually, with kernel 3.10.0-445.el7.x86_64, fprintd-0.5.0-4.0.el7_0.x86_64, > and > fprintd-pam-0.5.0-4.0.el7_0.x86_64, I get this even more confusing scenario: Those are the same versions mentioned in comment 0. Did something change? The best course of action to see movement on this bug would be to test the newer libfprint releases, as available in Fedora, with this device, as I don't have access to the full range of hardware, and that vendors do not provide specifications. Putting on needinfo until a newer upstream release is tested. (In reply to Bastien Nocera from comment #4) > (In reply to Matěj Cepl from comment #3) > > Actually, with kernel 3.10.0-445.el7.x86_64, fprintd-0.5.0-4.0.el7_0.x86_64, > > and > > fprintd-pam-0.5.0-4.0.el7_0.x86_64, I get this even more confusing scenario: > > Those are the same versions mentioned in comment 0. Did something change? > > The best course of action to see movement on this bug would be to test the > newer libfprint releases, as available in Fedora, with this device, as I > don't have access to the full range of hardware, and that vendors do not > provide specifications. > > Putting on needinfo until a newer upstream release is tested. Exactly the same results achieved with libfprint-0.7.0-3.el7.x86_64 fprintd-0.7.0-4.el7.x86_64 fprintd-pam-0.7.0-4.el7.x86_64 libfprint-devel-0.7.0-3.el7.x86_64 Created attachment 1313328 [details]
output of journalctl -xb
*** This bug has been marked as a duplicate of bug 1100801 *** |
Description of problem: When running fprind-enroll (both as normal user and as root; what's expected?) I get ~$ fprintd-enroll list_devices failed: No devices available ~$ Yet, lsusb -vv shows Bus 002 Device 003: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 17 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x138a Validity Sensors, Inc. idProduct 0x0017 Fingerprint Reader bcdDevice 0.78 iManufacturer 0 iProduct 0 iSerial 1 442ce215f961 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 4 Device Status: 0x0000 (Bus Powered) Version-Release number of selected component (if applicable): kernel-3.10.0-406.el7.x86_64 fprintd-0.5.0-4.0.el7_0.x86_64 fprintd-pam-0.5.0-4.0.el7_0.x86_64