Bug 1574883 - No support for 06cb:008a
Summary: No support for 06cb:008a
Alias: None
Product: Fedora
Classification: Fedora
Component: libfprint
Version: 28
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-04 09:11 UTC by Tom
Modified: 2018-05-04 10:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-04 10:00:15 UTC
Type: Bug

Attachments (Terms of Use)
lsusb -v output (54.68 KB, text/plain)
2018-05-04 09:11 UTC, Tom
no flags Details

System ID Private Priority Status Summary Last Updated
FreeDesktop.org 106282 0 None None None 2018-05-04 09:11:20 UTC

Description Tom 2018-05-04 09:11:21 UTC
Created attachment 1431146 [details]
lsusb -v output

Description of problem:

The fingerprint reader in current Toshiba B2B-models Portégé X30-D and X40-D (ad probably more) has a built-in FP-reader.
This device does not work at all. Likely no support exist in libfprint.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run F28 live or install F28
2. Go into user accounts management and look for FP-support.
3. None found.

Actual results:
Login with FP-support is not found in user account management.
This works well on older hardware.

Expected results:
Same FP-supported login with this hardware.

Additional info:
This is the output of lsusb:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
Bus 001 Device 004: ID 06cb:008a Synaptics, Inc. 
Bus 001 Device 003: ID 04f2:b5b5 Chicony Electronics Co., Ltd 
Bus 001 Device 002: ID 1fd2:6014  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Adding lsusb -v output.

Bug submitted at freedesktop.org bugzilla but no reply.

Comment 1 Bastien Nocera 2018-05-04 10:00:15 UTC
(In reply to Tom from comment #0)
> Bug submitted at freedesktop.org bugzilla but no reply.

We're not going to be able to do any more here. Unless you can reverse-engineer the protocol and write a driver, you'll just have to wait until somebody writes that driver upstream. It'll get into Fedora when that's done and tested.

Note You need to log in before you can comment on or make changes to this bug.