Description of problem: SELinux is preventing /usr/libexec/colord from read, search access on the directory /. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that colord should be allowed read search access on the 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 colord /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:colord_t:s0 Target Context system_u:object_r:user_home_t:s0 Target Objects / [ dir ] Source colord Source Path /usr/libexec/colord Port <Unknown> Host (removed) Source RPM Packages colord-0.1.23-1.fc17.i686 Target RPM Packages filesystem-3-2.fc17.i686 Policy RPM selinux-policy-3.10.0-167.fc17.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.8.4-102.fc17.i686 #1 SMP Sun Mar 24 13:20:55 UTC 2013 i686 i686 Alert Count 2 First Seen 2013-04-19 21:48:29 EEST Last Seen 2013-04-19 21:59:59 EEST Local ID 1238b401-8b7f-469c-b65d-0edc8ebcefe7 Raw Audit Messages type=AVC msg=audit(1366397999.388:42): avc: denied { read search } for pid=999 comm="colord" name="/" dev="sdb1" ino=2 scontext=system_u:system_r:colord_t:s0 tcontext=system_u:object_r:user_home_t:s0 tclass=dir type=SYSCALL msg=audit(1366397999.388:42): arch=i386 syscall=access success=no exit=EACCES a0=95f4578 a1=5 a2=4778fff4 a3=960be10 items=0 ppid=1 pid=999 auid=4294967295 uid=998 gid=996 euid=998 suid=998 fsuid=998 egid=996 sgid=996 fsgid=996 ses=4294967295 tty=(none) comm=colord exe=/usr/libexec/colord subj=system_u:system_r:colord_t:s0 key=(null) Hash: colord,colord_t,user_home_t,dir,read,search audit2allow #============= colord_t ============== allow colord_t user_home_t:dir { read search }; audit2allow -R #============= colord_t ============== allow colord_t user_home_t:dir { read search }; Additional info: hashmarkername: setroubleshoot kernel: 3.8.4-102.fc17.i686 type: libreport
Description of problem: Happens every time I mount an external hard drive Additional info: hashmarkername: setroubleshoot kernel: 3.8.13-100.fc17.i686 type: libreport
git log commit 30692e54423efef8ee064a6cc0eda3e7b7d54b75 allows this in Rawhide.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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.10.0-171.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-171.fc17
Package selinux-policy-3.10.0-171.fc17: * should fix your issue, * was pushed to the Fedora 17 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.10.0-171.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13082/selinux-policy-3.10.0-171.fc17 then log in and leave karma (feedback).
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.