SELinux is preventing /usr/libexec/polkit-1/polkitd from 'read' accesses on the file /etc/localtime. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that polkitd should be allowed read access on the localtime 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 /usr/libexec/polkit-1/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:etc_runtime_t:s0 Target Objects /etc/localtime [ file ] Source polkitd Source Path /usr/libexec/polkit-1/polkitd Port <Desconocido> Host (removed) Source RPM Packages polkit-0.98-4.fc14 Target RPM Packages glibc-2.12.90-17 Policy RPM selinux-policy-3.9.7-3.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.10-74.fc14.i686 #1 SMP Thu Dec 23 16:17:40 UTC 2010 i686 i686 Alert Count 9 First Seen mié 29 dic 2010 18:54:04 CET Last Seen vie 31 dic 2010 13:16:51 CET Local ID 0685b8a8-ebba-4511-8288-cf4f46deb076 Raw Audit Messages type=AVC msg=audit(1293797811.290:28): avc: denied { read } for pid=1472 comm="polkitd" name="localtime" dev=sda1 ino=74273 scontext=system_u:system_r:policykit_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_runtime_t:s0 tclass=file polkitd,policykit_t,etc_runtime_t,file,read type=SYSCALL msg=audit(1293797811.290:28): arch=i386 syscall=open success=no exit=EACCES a0=825a91 a1=0 a2=1b6 a3=823d1a items=0 ppid=1471 pid=1472 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) polkitd,policykit_t,etc_runtime_t,file,read #============= policykit_t ============== allow policykit_t etc_runtime_t:file read;
Execute # restorecon -R -v /etc/localtime We are trying to figure out where the problem is. Please reopen if the problem happens again.
*** Bug 666543 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 666557 ***