Description of problem: Plug in power supply SELinux is preventing udevadm from 'open' accesses on the file /etc/selinux/targeted/contexts/files/file_contexts.bin. ***** Plugin catchall (100. confidence) suggests ************************** If sie denken, dass es udevadm standardmäßig erlaubt sein sollte, open Zugriff auf file_contexts.bin file zu erhalten. 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 'udevadm' --raw | audit2allow -M my-udevadm # semodule -X 300 -i my-udevadm.pp Additional Information: Source Context system_u:system_r:tlp_t:s0 Target Context unconfined_u:object_r:file_context_t:s0 Target Objects /etc/selinux/targeted/contexts/files/file_contexts .bin [ file ] Source udevadm Source Path udevadm Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages selinux-policy-targeted-3.13.1-225.11.fc25.noarch Policy RPM selinux-policy-3.13.1-225.11.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.10.5-200.fc25.x86_64 #1 SMP Wed Mar 22 20:37:08 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2017-03-28 19:22:57 CEST Last Seen 2017-03-28 19:22:57 CEST Local ID c2a80340-e11b-49ef-bd1e-a8cf7e7a84a2 Raw Audit Messages type=AVC msg=audit(1490721777.351:205): avc: denied { open } for pid=3898 comm="udevadm" path="/etc/selinux/targeted/contexts/files/file_contexts.bin" dev="dm-1" ino=4326954 scontext=system_u:system_r:tlp_t:s0 tcontext=unconfined_u:object_r:file_context_t:s0 tclass=file permissive=1 Hash: udevadm,tlp_t,file_context_t,file,open Version-Release number of selected component: selinux-policy-3.13.1-225.11.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.5-200.fc25.x86_64 type: libreport Potential duplicate: bug 1416967
Description of problem: boot the system Version-Release number of selected component: selinux-policy-3.13.1-225.16.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.16-200.fc25.x86_64 type: libreport
Description of problem: boot the system Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.5-200.fc25.x86_64 type: libreport
*** Bug 1416967 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.