SELinux is preventing /usr/libexec/colord from 'getattr' accesses on the filesystem /media/Daten. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that colord should be allowed getattr access on the Daten filesystem 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 colord /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:colord_t:s0-s0:c0.c1023 Target Context system_u:object_r:fusefs_t:s0 Target Objects /media/Daten [ filesystem ] Source colord Source Path /usr/libexec/colord Port <Unknown> Host (removed) Source RPM Packages colord-0.1.1-3.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-21.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux paullaptop 2.6.38.5-22.fc15.i686 #1 SMP Mon May 2 20:17:28 UTC 2011 i686 i686 Alert Count 1 First Seen Mon 09 May 2011 12:36:51 AM CEST Last Seen Mon 09 May 2011 12:36:51 AM CEST Local ID 4008f710-49ba-4470-b547-8c31dd01bba3 Raw Audit Messages type=AVC msg=audit(1304894211.756:93): avc: denied { getattr } for pid=3151 comm="colord" name="/" dev=sda3 ino=5 scontext=system_u:system_r:colord_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fusefs_t:s0 tclass=filesystem type=SYSCALL msg=audit(1304894211.756:93): arch=i386 syscall=statfs64 success=yes exit=0 a0=976be40 a1=54 a2=bfc92e2c a3=8055e63 items=0 ppid=1 pid=3151 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=colord exe=/usr/libexec/colord subj=system_u:system_r:colord_t:s0-s0:c0.c1023 key=(null) Hash: colord,colord_t,fusefs_t,filesystem,getattr audit2allow #============= colord_t ============== allow colord_t fusefs_t:filesystem getattr; audit2allow -R #============= colord_t ============== allow colord_t fusefs_t:filesystem getattr;
Please use the policy from updates-testing repo # yum update selinux-policy --enablerepo=updates-testing
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.