Description of problem: SELinux is preventing /usr/sbin/NetworkManager from using the 'setsched' accesses on a process. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that NetworkManager should be allowed setsched access on processes labeled kernel_t 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: # grep NetworkManager /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:NetworkManager_t:s0 Target Context system_u:system_r:kernel_t:s0 Target Objects [ process ] Source NetworkManager Source Path /usr/sbin/NetworkManager Port <Unknown> Host (removed) Source RPM Packages NetworkManager-0.9.8.2-1.fc18.i686 Target RPM Packages Policy RPM selinux-policy-3.11.1-106.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.4-101.fc18.i686 #1 SMP Thu Oct 10 14:33:33 UTC 2013 i686 i686 Alert Count 7 First Seen 2013-10-26 17:00:30 CEST Last Seen 2013-10-28 15:56:57 CET Local ID d5e79ab9-bfe8-4257-a825-e5323a2cde89 Raw Audit Messages type=AVC msg=audit(1382972217.465:418): avc: denied { setsched } for pid=685 comm="NetworkManager" scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process type=SYSCALL msg=audit(1382972217.465:418): arch=i386 syscall=socketcall success=yes exit=EPIPE a0=10 a1=bfedf440 a2=b72e5000 a3=0 items=0 ppid=1 pid=685 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=NetworkManager exe=/usr/sbin/NetworkManager subj=system_u:system_r:NetworkManager_t:s0 key=(null) Hash: NetworkManager,NetworkManager_t,kernel_t,process,setsched audit2allow #============= NetworkManager_t ============== allow NetworkManager_t kernel_t:process setsched; audit2allow -R require { type NetworkManager_t; } #============= NetworkManager_t ============== kernel_load_module(NetworkManager_t) Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.11.4-101.fc18.i686 type: libreport Potential duplicate: bug 1010537
Fedora 20 has this rule.
also added to f18 branch.
Description of problem: Wireless connection was not connected. Checked dmesg to ensure wireless b43 module loaded successfully. Turned wireless off and turned wireless back on. Wireless network connection established and SELinux policy violation occured. This began after most recent updates. Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.7-100.fc18.x86_64 type: libreport
Description of problem: Turn off Wireless Network. Turn on Wireless Network. Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.9-100.fc18.x86_64 type: libreport
selinux-policy-3.11.1-108.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-108.fc18
Package selinux-policy-3.11.1-108.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-108.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23716/selinux-policy-3.11.1-108.fc18 then log in and leave karma (feedback).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Description of problem: Logged in after bringing laptop from sleep. Additional info: reporter: libreport-2.1.9 hashmarkername: setroubleshoot kernel: 3.11.10-100.fc18.x86_64 type: libreport
selinux-policy-3.11.1-108.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.