Hide Forgot
Description of problem: SELinux is preventing pcscd from using the 'wake_alarm' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If sie denken, dass pcscd standardmäßig wake_alarm Berechtigung haben sollten. Then sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Do allow this access for now by executing: # ausearch -c 'pcscd' --raw | audit2allow -M my-pcscd # semodule -X 300 -i my-pcscd.pp Additional Information: Source Context system_u:system_r:pcscd_t:s0 Target Context system_u:system_r:pcscd_t:s0 Target Objects Unknown [ capability2 ] Source pcscd Source Path pcscd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.19.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 Alert Count 695 First Seen 2016-11-01 08:02:20 CET Last Seen 2016-11-02 21:01:06 CET Local ID bcd26d0b-9855-45a3-92c4-7ac71f61d530 Raw Audit Messages type=AVC msg=audit(1478116866.762:286): avc: denied { wake_alarm } for pid=1384 comm="pcscd" capability=35 scontext=system_u:system_r:pcscd_t:s0 tcontext=system_u:system_r:pcscd_t:s0 tclass=capability2 permissive=0 Hash: pcscd,pcscd_t,pcscd_t,capability2,wake_alarm Version-Release number of selected component: selinux-policy-3.13.1-191.19.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.4-200.fc24.x86_64 type: libreport Potential duplicate: bug 1381510
Description of problem: The AVC occured at boot. Probably due to a kernel update, from kernel-4.7.9-200.fc24.x86_64 to kernel-4.8.4-200.fc24.x86_64. Version-Release number of selected component: selinux-policy-3.13.1-191.19.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.4-200.fc24.x86_64 type: libreport
Description of problem: Tried to use GnuPG with an already-inserted Sigilance smart card in a Lenovo ThinkPad T560 reader. Version-Release number of selected component: selinux-policy-3.13.1-191.19.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.4-200.fc24.x86_64 type: libreport
I don't think this is directly related to a kernel update. I believe this started showing up sometime back in mid-October for me. Update history from October 10th shows: Upgraded selinux-policy-3.13.1-191.17.fc24.noarch @updates Upgrade 3.13.1-191.18.fc24.noarch @updates Upgraded selinux-policy-targeted-3.13.1-191.17.fc24.noarch @updates Upgrade 3.13.1-191.18.fc24.noarch @updates I am unable to downgrade: $ sudo dnf downgrade selinux-policy Contacting OpenClient Router for restricted repository information Added restricted repo: RHEL-7-x86_64-crashplan Added restricted repo: Fedora-24-x86_64-Licensed Last metadata expiration check: 2:38:07 ago on Tue Nov 8 10:37:33 2016. Error: package firewalld-0.4.3.3-1.fc24.noarch conflicts with selinux-policy < 3.13.1-191.fc24.3 provided by selinux-policy-3.13.1-190.fc24.noarch (try to add '--allowerasing' to command line to replace conflicting packages) $
Messages stopped after updated to updates-testing version(s) around 2016/11/08 13:20 CST: $ sudo dnf --enable=updates-testing update selinux-policy selinux-policy-targeted ... Running transaction Upgrading : selinux-policy-3.13.1-191.20.fc24.noarch 1/4 Upgrading : selinux-policy-targeted-3.13.1-191.20.fc24.noarch 2/4 Cleanup : selinux-policy-targeted-3.13.1-191.19.fc24.noarch 3/4 Cleanup : selinux-policy-3.13.1-191.19.fc24.noarch 4/4 Verifying : selinux-policy-3.13.1-191.20.fc24.noarch 1/4 Verifying : selinux-policy-targeted-3.13.1-191.20.fc24.noarch 2/4 Verifying : selinux-policy-3.13.1-191.19.fc24.noarch 3/4 Verifying : selinux-policy-targeted-3.13.1-191.19.fc24.noarch 4/4 Upgraded: selinux-policy.noarch 3.13.1-191.20.fc24 selinux-policy-targeted.noarch 3.13.1-191.20.fc24 Complete! $
Description of problem: Starting up the daemon Version-Release number of selected component: selinux-policy-3.13.1-191.19.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.6-201.fc24.x86_64 type: libreport
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.