Description of problem: Change timezone in gnome-control-center Additional info: libreport version: 2.0.18 kernel: 3.6.5-2.fc18.x86_64 description: :SELinux is preventing /usr/lib/systemd/systemd-timedated from 'ioctl' accesses on the chr_file /dev/rtc0. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that systemd-timedated should be allowed ioctl access on the rtc0 chr_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 systemd-timedat /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context system_u:system_r:gnomeclock_t:s0 :Target Context system_u:object_r:clock_device_t:s0 :Target Objects /dev/rtc0 [ chr_file ] :Source systemd-timedat :Source Path /usr/lib/systemd/systemd-timedated :Port <Unknown> :Host (removed) :Source RPM Packages systemd-195-2.fc18.x86_64 :Target RPM Packages :Policy RPM selinux-policy-3.11.1-46.fc18.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Permissive :Host Name (removed) :Platform Linux (removed) 3.6.5-2.fc18.x86_64 #1 SMP Thu Nov : 1 00:39:17 UTC 2012 x86_64 x86_64 :Alert Count 1 :First Seen 2012-11-07 06:55:15 EST :Last Seen 2012-11-07 06:55:15 EST :Local ID 344f6f37-f56b-41fc-af3c-299c29457314 : :Raw Audit Messages :type=AVC msg=audit(1352289315.33:264): avc: denied { ioctl } for pid=7391 comm="systemd-timedat" path="/dev/rtc0" dev="devtmpfs" ino=8218 scontext=system_u:system_r:gnomeclock_t:s0 tcontext=system_u:object_r:clock_device_t:s0 tclass=chr_file : : :type=SYSCALL msg=audit(1352289315.33:264): arch=x86_64 syscall=ioctl success=yes exit=0 a0=5 a1=4024700a a2=7f16195fdf40 a3=ffffffffffffc414 items=0 ppid=1 pid=7391 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-timedat exe=/usr/lib/systemd/systemd-timedated subj=system_u:system_r:gnomeclock_t:s0 key=(null) : :Hash: systemd-timedat,gnomeclock_t,clock_device_t,chr_file,ioctl : :audit2allow : :#============= gnomeclock_t ============== :allow gnomeclock_t clock_device_t:chr_file ioctl; : :audit2allow -R : :#============= gnomeclock_t ============== :allow gnomeclock_t clock_device_t:chr_file ioctl; :
Created attachment 640172 [details] File: type
Created attachment 640173 [details] File: hashmarkername
Matthius does gnomeclock actually set the realtime clock?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.