Bug 1198844

Summary: fprintd-pam is in Standard comps group, should be in Hardware Support
Product: [Fedora] Fedora Reporter: Dan Mossor [danofsatx] <danofsatx>
Component: compsAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: sgallagh, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 12:55:54 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:

Description Dan Mossor [danofsatx] 2015-03-04 22:34:05 UTC 
In reviewing the package list for Fedora Server, it was discovered that the fprintd-pam package is included in the Standard comp group. This also pulls in the fprintd package.

The fprintd-pam and fprintd packages, with the associated libfprint library, are specifically for systems equipped with fingerprint reader devices. With out the associated hardware, fprintd enters the following into the journal every 10 seconds to 10 hours - there seems to be no rhyme or reason to the startup of the service.

Mar 04 11:32:00 redmine.example.net fprintd[10552]: Launching FprintObject
Mar 04 11:32:00 redmine.example.net fprintd[10552]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 04 11:32:00 redmine.example.net fprintd[10552]: ** Message: entering main loop
Mar 04 11:32:30 redmine.example.net fprintd[10552]: ** Message: No devices in use, exit
Mar 04 11:33:13 redmine.example.net fprintd[11200]: Launching FprintObject
Mar 04 11:33:13 redmine.example.net fprintd[11200]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 04 11:33:13 redmine.example.net fprintd[11200]: ** Message: entering main loop
Mar 04 11:33:43 redmine.example.net fprintd[11200]: ** Message: No devices in use, exit
Mar 04 11:40:56 redmine.example.net fprintd[13261]: Launching FprintObject
Mar 04 11:40:56 redmine.example.net fprintd[13261]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 04 11:40:56 redmine.example.net fprintd[13261]: ** Message: entering main loop
Mar 04 11:41:26 redmine.example.net fprintd[13261]: ** Message: No devices in use, exit
Mar 04 11:42:07 redmine.example.net fprintd[13296]: Launching FprintObject
Mar 04 11:42:07 redmine.example.net fprintd[13296]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 04 11:42:07 redmine.example.net fprintd[13296]: ** Message: entering main loop
Mar 04 11:42:37 redmine.example.net fprintd[13296]: ** Message: No devices in use, exit
Mar 04 11:43:20 redmine.example.net fprintd[13307]: Launching FprintObject
Mar 04 11:43:20 redmine.example.net fprintd[13307]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
Mar 04 11:43:20 redmine.example.net fprintd[13307]: ** Message: entering main loop
Mar 04 11:43:49 redmine.example.net fprintd[13307]: ** Message: No devices in use, exit

As the fingerprint reader is a specific hardware device required for the operation of this service, the fprintd-pam package should be moved to the Hardware Support group, and removed from the Standard group. Additionally, the fprintd-pam package is also included in the Fedora Workstation and GNOME Desktop Environment groups.

The removal of this package may require some additional configuration of pam to not expect it to be there, unless pam is configured at install with only the packages available on the system.
Comment 1 Fedora End Of Life 2016-07-19 12:55:54 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.