Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I have a similar problem. I'm using fedora 20 on Dell Vostro 5470. My fingerprint device is 138a:0011. I think the driver below will resolve the problem:
https://bugs.freedesktop.org/show_bug.cgi?id=61692
(In reply to Bastien Nocera from comment #3)
> This isn't even upstream yet, so it will have to wait until it is before we
> can consider it for inclusion in a RHEL version.
>
> So, nak'ing for RHEL 7.1.
Update: it must me upstream by now because the device works in F21.
Update: may be it's just the failing hardware in my laptop.
BUT
The fingerprint readers works bad - it accepts only one out of 3-5 attempts after initial enroll.
I've rebuilt the packages (rpmbuild --rebuild) from Fedora 22 and found no difference in the (awful) sensor operation.
Is the fingerprint supported in RedHat 7.4?
In my thinkpad X1 doesn't show up!
Fedora 27 is running with no problems...
Can somebody anwer this?
Thank you...
Updated build, built as libfprint-0.8.2-1.el7
0.8.2 downgrades some assertions to be warnings, which were causing crashes instead of being worked-around.
Customer tested RHEL 7.6 Snapshot 3 on a Lenovo T460:
Testing was done on a T460 and it works after doing the change below to the fprintd.service file. Without the "-t" option the fprintd is terminating after being idle for a few minutes.
sudo vi /usr/lib/systemd/system/fprintd.service
changed this: ExecStart=/usr/libexec/fprintd
to this: ExecStart=/usr/libexec/fprintd -t
[d120807@oc6131864761 ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 5986:0706 Acer, Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[d120807@oc6131864761 ~]$
(In reply to Paul Gozart from comment #19)
> Customer tested RHEL 7.6 Snapshot 3 on a Lenovo T460:
>
> Testing was done on a T460 and it works after doing the change below to the
> fprintd.service file. Without the "-t" option the fprintd is terminating
> after being idle for a few minutes.
That's how it's supposed to work, fprintd is autostarted via D-Bus and systemd.
(In reply to Bastien Nocera from comment #20)
> (In reply to Paul Gozart from comment #19)
> > Customer tested RHEL 7.6 Snapshot 3 on a Lenovo T460:
> >
> > Testing was done on a T460 and it works after doing the change below to the
> > fprintd.service file. Without the "-t" option the fprintd is terminating
> > after being idle for a few minutes.
>
> That's how it's supposed to work, fprintd is autostarted via D-Bus and
> systemd.
Thanks for fixing this!
Customer replied:
Thanks for the update. Engineering is right, I got the fingerprint reader to work this way on the T460:
1. Activities -> Authentication -> Advanced Options -> Enable fingerprint reader support
2. Activities -> Settings -> Details -> Users -> Enable Fingerprint Login and follow steps to register own fingerprint
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:3206