Description of problem: SELinux is preventing Chrome_ChildIOT from 'block_suspend' accesses on the capability2 . ***** Plugin catchall (100. confidence) suggests *************************** If you believe that Chrome_ChildIOT should be allowed block_suspend access on the 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: # grep Chrome_ChildIOT /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c 0.c1023 Target Context unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c 0.c1023 Target Objects [ capability2 ] Source Chrome_ChildIOT Source Path Chrome_ChildIOT Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.11.1-86.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.8.5-201.fc18.x86_64 #1 SMP Thu Mar 28 21:01:19 UTC 2013 x86_64 x86_64 Alert Count 3 First Seen 2013-04-10 16:30:38 CEST Last Seen 2013-04-10 16:31:33 CEST Local ID 9c25a9f5-ed96-401f-90e5-3ed2453053ba Raw Audit Messages type=AVC msg=audit(1365604293.128:8821): avc: denied { block_suspend } for pid=1145 comm="Chrome_ChildIOT" capability=36 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tclass=capability2 Hash: Chrome_ChildIOT,chrome_sandbox_t,chrome_sandbox_t,capability2,block_suspend audit2allow #============= chrome_sandbox_t ============== allow chrome_sandbox_t self:capability2 block_suspend; audit2allow -R require { type chrome_sandbox_t; class capability2 block_suspend; } #============= chrome_sandbox_t ============== allow chrome_sandbox_t self:capability2 block_suspend; Additional info: hashmarkername: setroubleshoot kernel: 3.8.5-201.fc18.x86_64 type: libreport
So the question is should we allow a gnome plugin to block the machine from suspending?
This was the result of an automatic bugreport from ABRT. I don't think it really caused a problem.
4dcf822c610140c67f309c027a4226e9a4277da8 fixes this in git.
back ported.
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.
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.