Bug 1398959

Summary:	Finterprint reader is not called after upgrade to Fedora 25
Product:	[Fedora] Fedora	Reporter:	jezekus
Component:	fprintd	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	bnocera
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-13 16:59:58 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:

Description jezekus 2016-11-27 16:17:15 UTC

Description of problem:

After upgrade of Fedora 24 to Fedora 25 using dnf system-upgrade plugin fingerprint reader is not called on lock screen, login screen or sudo.

Fingerprint reader itself is working correctly and fprintd-enroll or fprintd-validate calls fingerprint reader as expected.

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

Fedora 25 - kernel 4.8.8-300.fc25.x86_64
fprintd.x86_64                         0.7.0-1.fc25                      @fedora
fprintd-pam.x86_64                     0.7.0-1.fc25                      @fedora

How reproducible:
Upgrade Fedora 24 to Fedora 25 and try to use fingerprint reader for authentication.


Steps to Reproduce:
1.Get working fingerprint reader for unlocking the screen, sudo and other authentication in Fedora 24
2. Upgrade to Fedora 25
3. Try to use fingerprint for unlocking the screen.

Actual results:
Fingerprint is not ready for reading (Lenovo X220 and T440 has led when fingerprint reader is active - this LED is not blinking) and user is not able to authenticate itself using fingerprint reader.

Expected results:
Fingerprint reader will be ready and authenticate the user and in case of Lenovo LED will blink.

Tested on Lenovo X220 and Lenovo T440

Comment 1 jezekus 2016-12-13 16:59:58 UTC


*** This bug has been marked as a duplicate of bug 1398371 ***