Summary: SELinux is preventing /usr/lib/chromium-browser/chrome-sandbox access to a leaked fifo_file file descriptor. Detailed Description: [SELinux is in permissive mode. This access was not denied.] SELinux denied access requested by the chrome-sandbox command. It looks like this is either a leaked descriptor or chrome-sandbox output was redirected to a file it is not allowed to access. Leaks usually can be ignored since SELinux is just closing the leak and reporting the error. The application does not use the descriptor, so it will run properly. If this is a redirection, you will not get output in the fifo_file. You should generate a bugzilla on selinux-policy, and it will get routed to the appropriate package. You can safely ignore this avc. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Additional Information: Source Context unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c 0.c1023 Target Context unconfined_u:unconfined_r:unconfined_mono_t:s0-s0: c0.c1023 Target Objects fifo_file [ fifo_file ] Source chrome-sandbox Source Path /usr/lib/chromium-browser/chrome-sandbox Port <Unknown> Host (removed) Source RPM Packages chromium-6.0.486.0-1.fc13 Target RPM Packages Policy RPM selinux-policy-3.7.19-47.fc13 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Plugin Name leaks Host Name (removed) Platform Linux (removed) 2.6.33.6-147.2.4.fc13.i686 #1 SMP Fri Jul 23 17:27:40 UTC 2010 i686 i686 Alert Count 4 First Seen Sun 22 Aug 2010 17:26:18 CEST Last Seen Sun 22 Aug 2010 19:24:58 CEST Local ID d4c05aee-7a98-4c7a-85da-2f2f8fa56910 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1282497898.912:30582): avc: denied { write } for pid=13360 comm="chrome-sandbox" path="pipe:[853377]" dev=pipefs ino=853377 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:unconfined_r:unconfined_mono_t:s0-s0:c0.c1023 tclass=fifo_file node=(removed) type=SYSCALL msg=audit(1282497898.912:30582): arch=40000003 syscall=11 success=yes exit=0 a0=8843bcc a1=8842790 a2=885f000 a3=8842790 items=0 ppid=13358 pid=13360 auid=500 uid=500 gid=500 euid=0 suid=0 fsuid=0 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm="chrome-sandbox" exe="/usr/lib/chromium-browser/chrome-sandbox" subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 key=(null) Hash String generated from leaks,chrome-sandbox,chrome_sandbox_t,unconfined_mono_t,fifo_file,write audit2allow suggests: #============= chrome_sandbox_t ============== allow chrome_sandbox_t unconfined_mono_t:fifo_file write;
Do you have some mono application that is starting chromium?
Can't be sure either way, but I was testing Banshee, maybe it tried using Chromium as it default browser on my system.
You can add these rules for now using # grep avc /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Fixed in selinux-policy-3.9.1-3.fc14
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping