Description of problem: Follow update of Google Chrome (beta) SELinux is preventing /opt/google/chrome/chrome from 'append' accesses on the file /home/sdstern/libpeerconnection.log. ***** Plugin restorecon (99.5 confidence) suggests ************************* If you want to fix the label. /home/sdstern/libpeerconnection.log default label should be user_home_t. Then you can run restorecon. Do # /sbin/restorecon -v /home/sdstern/libpeerconnection.log ***** Plugin catchall (1.49 confidence) suggests *************************** If you believe that chrome should be allowed append access on the libpeerconnection.log file 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 /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:object_r:user_home_dir_t:s0 Target Objects /home/sdstern/libpeerconnection.log [ file ] Source chrome Source Path /opt/google/chrome/chrome Port <Unknown> Host (removed) Source RPM Packages google-chrome-beta-28.0.1500.20-201172.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-96.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 3.9.2-200.fc18.x86_64 #1 SMP Mon May 13 13:59:47 UTC 2013 x86_64 x86_64 Alert Count 2 First Seen 2013-05-24 09:25:31 CDT Last Seen 2013-05-24 09:33:39 CDT Local ID d46415ec-78d0-48ac-850d-d2ea4f4ae1f3 Raw Audit Messages type=AVC msg=audit(1369406019.36:1326): avc: denied { append } for pid=20481 comm="chrome" name="libpeerconnection.log" dev="sda5" ino=50332110 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=file type=AVC msg=audit(1369406019.36:1326): avc: denied { open } for pid=20481 comm="chrome" path="/home/sdstern/libpeerconnection.log" dev="sda5" ino=50332110 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=file type=SYSCALL msg=audit(1369406019.36:1326): arch=x86_64 syscall=open success=yes exit=EACCES a0=7f5b10219a38 a1=441 a2=1b6 a3=0 items=0 ppid=0 pid=20481 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=2 tty=(none) comm=chrome exe=/opt/google/chrome/chrome subj=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 key=(null) Hash: chrome,chrome_sandbox_t,user_home_dir_t,file,append audit2allow #============= chrome_sandbox_t ============== allow chrome_sandbox_t user_home_dir_t:file { open append }; audit2allow -R require { type chrome_sandbox_t; type user_home_dir_t; class file { open append }; } #============= chrome_sandbox_t ============== allow chrome_sandbox_t user_home_dir_t:file { open append }; Additional info: hashmarkername: setroubleshoot kernel: 3.9.2-200.fc18.x86_64 type: libreport
This is a known problem in chrome which I beleive is now fixed at google.
*** Bug 975621 has been marked as a duplicate of this bug. ***