Hide Forgot
SELinux is preventing /opt/google/chrome/chrome from 'write' accesses on the directory /home/philipp. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that chrome should be allowed write access on the philipp directory 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/philipp [ dir ] Source chrome Source Path /opt/google/chrome/chrome Port <Unbekannt> Host (removed) Source RPM Packages google-chrome-stable-12.0.742.91-87961 Target RPM Packages Policy RPM selinux-policy-3.9.16-26.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.7-30.fc15.x86_64 #1 SMP Fri May 27 05:15:53 UTC 2011 x86_64 x86_64 Alert Count 2 First Seen Mit 15 Jun 2011 00:12:00 CEST Last Seen Mit 15 Jun 2011 00:12:00 CEST Local ID ccecafef-615b-4c40-8c18-10246137d8f1 Raw Audit Messages type=AVC msg=audit(1308089520.23:80): avc: denied { write } for pid=4982 comm="chrome" name="philipp" dev=dm-2 ino=4980737 scontext=unconfined_u:unconfined_r:chrome_sandbox_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=dir type=SYSCALL msg=audit(1308089520.23:80): arch=x86_64 syscall=open success=no exit=EACCES a0=57f83a8 a1=441 a2=1b6 a3=69654b203a676f6c items=0 ppid=0 pid=4982 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=pts1 ses=1 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,dir,write audit2allow #============= chrome_sandbox_t ============== #!!!! The source type 'chrome_sandbox_t' can write to a 'dir' of the following types: # user_fonts_cache_t, chrome_sandbox_tmpfs_t, chrome_sandbox_tmp_t, cgroup_t, tmp_t, tmpfs_t allow chrome_sandbox_t user_home_dir_t:dir write; audit2allow -R #============= chrome_sandbox_t ============== #!!!! The source type 'chrome_sandbox_t' can write to a 'dir' of the following types: # user_fonts_cache_t, chrome_sandbox_tmpfs_t, chrome_sandbox_tmp_t, cgroup_t, tmp_t, tmpfs_t allow chrome_sandbox_t user_home_dir_t:dir write;
Any idea what file/directory chrome-sandbox was trying to write to?
restorecon -R -v /home Fixed in current release.