Description of problem: SELinux is preventing fprintd from 'wake_alarm' accesses on the capability2 Unknown. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that fprintd should be allowed wake_alarm access on the Unknown capability2 by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'fprintd' --raw | audit2allow -M my-fprintd # semodule -X 300 -i my-fprintd.pp Additional Information: Source Context system_u:system_r:fprintd_t:s0 Target Context system_u:system_r:fprintd_t:s0 Target Objects Unknown [ capability2 ] Source fprintd Source Path fprintd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-204.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.8.0-0.rc0.git2.1.fc25.x86_64 #1 SMP Thu Jul 28 19:11:53 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-07-29 16:10:22 CEST Last Seen 2016-07-29 16:10:22 CEST Local ID 93e84f93-d16a-4642-82cb-dbb12be55405 Raw Audit Messages type=AVC msg=audit(1469801422.831:258): avc: denied { wake_alarm } for pid=2077 comm="fprintd" capability=35 scontext=system_u:system_r:fprintd_t:s0 tcontext=system_u:system_r:fprintd_t:s0 tclass=capability2 permissive=1 Hash: fprintd,fprintd_t,fprintd_t,capability2,wake_alarm Version-Release number of selected component: selinux-policy-3.13.1-204.fc25.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc0.git2.1.fc25.x86_64 type: libreport
Description of problem: Fingerprint scanner is causing SELinux alerts Version-Release number of selected component: selinux-policy-3.13.1-205.fc26.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc0.git3.1.fc26.x86_64 type: libreport
Description of problem: Error popped up after login to desktop Version-Release number of selected component: selinux-policy-3.13.1-206.fc26.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc0.git5.1.fc26.x86_64 type: libreport
This is also happening on Fedora 24 since selinux-policy-3.13.1-191.8.fc24.noarch, it happens most anytime I use sudo and type in a password. time->Wed Aug 10 11:16:23 2016 type=AVC msg=audit(1470849383.290:336): avc: denied { wake_alarm } for pid=3154 comm="fprintd" capability=35 scontext=system_u:system_r:fprintd_t:s0 tcontext=system_u:system_r:fprintd_t:s0 tclass=capability2 permissive=0
Description of problem: Started dnf --refresh upgrade and this popped up. Version-Release number of selected component: selinux-policy-3.13.1-207.fc26.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc1.git0.1.fc26.x86_64 type: libreport
Rado, Any ideas here?
We should dontaudit this and then get fprintd to fix the issue. But I am not sure what is causing it.
Dan, After discussion with Radovan, maybe fprintd block suspending during authentication. Maybe we should allow it.
selinux-policy-3.13.1-208.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-662487f8f1
Description of problem: This popped up on me on first boot after a default Workstation Live install (Fedora-Workstation-Live-x86_64-25-20160815.n.2.iso). I just started terminal and ran dnf, nothing else. Not sure whether this occurred before or after. Version-Release number of selected component: selinux-policy-3.13.1-207.fc25.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc1.git0.1.fc25.x86_64 type: libreport
Proposing as a Final blocker: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop. " https://fedoraproject.org/wiki/Fedora_25_Final_Release_Criteria#SELinux_and_crash_notifications
*** Bug 1366852 has been marked as a duplicate of this bug. ***
selinux-policy-3.13.1-208.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Description of problem: I've encountered this while using Gnome, some minutes after the login. I don't think I did a specific action. Version-Release number of selected component: selinux-policy-3.13.1-207.fc25.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.0-0.rc0.git3.1.fc25.x86_64 type: libreport