Hide Forgot
SELinux is preventing /usr/libexec/polkit-1/polkitd from 'read' accesses on the directory ConsoleKit. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that polkitd should be allowed read access on the ConsoleKit 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 polkitd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:policykit_t:s0-s0:c0.c1023 Target Context system_u:object_r:tmpfs_t:s0 Target Objects ConsoleKit [ dir ] Source polkitd Source Path /usr/libexec/polkit-1/polkitd Port <Unknown> Host (removed) Source RPM Packages polkit-0.101-4.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-6.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Thu 31 Mar 2011 10:01:55 AM GMT Last Seen Thu 31 Mar 2011 10:01:55 AM GMT Local ID 03509391-d951-4211-ad26-a6d97aa4ef78 Raw Audit Messages type=AVC msg=audit(1301565715.93:129): avc: denied { read } for pid=917 comm="polkitd" name="ConsoleKit" dev=tmpfs ino=17816 scontext=system_u:system_r:policykit_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir type=SYSCALL msg=audit(1301565715.93:129): arch=x86_64 syscall=inotify_add_watch success=yes exit=EBUSY a0=c a1=a7bea0 a2=1002fce a3=1 items=0 ppid=1 pid=917 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=polkitd exe=/usr/libexec/polkit-1/polkitd subj=system_u:system_r:policykit_t:s0-s0:c0.c1023 key=(null) Hash: polkitd,policykit_t,tmpfs_t,dir,read audit2allow #============= policykit_t ============== allow policykit_t tmpfs_t:dir read; audit2allow -R #============= policykit_t ============== allow policykit_t tmpfs_t:dir read;
*** This bug has been marked as a duplicate of bug 692459 ***