Hide Forgot
Description of problem: The following spillage shows up in logs over and over: setroubleshoot: SELinux is preventing /usr/libexec/mission-control-5 from remove_name access on the directory accounts-goa.cfg.CPRI4W. For complete SELinux messages. run sealert -l a2c50f89-e56c-4c72-b72c-30f9beaa9d31 setroubleshoot: SELinux is preventing /usr/libexec/mission-control-5 from write access on the file user. For complete SELinux messages. run sealert -l 82110924-588f-46f1-b496-d270da8c0bb3 Running 'sealert -l a2c50f89-e56c-4c72-b72c-30f9beaa9d31' and 'sealert -l 82110924-588f-46f1-b496-d270da8c0bb3' gives the following: # sealert -l a2c50f89-e56c-4c72-b72c-30f9beaa9d31 SELinux is preventing /usr/libexec/mission-control-5 from remove_name access on the directory accounts-goa.cfg.CPRI4W. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that mission-control-5 should be allowed remove_name access on the accounts-goa.cfg.CPRI4W 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 mission-control /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 Target Context system_u:object_r:xdm_var_lib_t:s0 Target Objects accounts-goa.cfg.CPRI4W [ dir ] Source mission-control Source Path /usr/libexec/mission-control-5 Port <Unknown> Host some.host Source RPM Packages telepathy-mission-control-5.14.0-2.fc18.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-105.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name some.host Platform Linux some.host 3.10.14-100.fc18.x86_64 #1 SMP Fri Oct 4 15:55:52 UTC 2013 x86_64 x86_64 Alert Count 27 First Seen 2013-05-06 09:47:13 MDT Last Seen 2013-10-10 11:13:58 MDT Local ID a2c50f89-e56c-4c72-b72c-30f9beaa9d31 Raw Audit Messages type=AVC msg=audit(1381425238.577:129): avc: denied { remove_name } for pid=6598 comm="mission-control" name="accounts-goa.cfg.CPRI4W" dev="sda3" ino=9830670 scontext=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=dir type=AVC msg=audit(1381425238.577:129): avc: denied { rename } for pid=6598 comm="mission-control" name="accounts-goa.cfg.CPRI4W" dev="sda3" ino=9830670 scontext=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file type=AVC msg=audit(1381425238.577:129): avc: denied { unlink } for pid=6598 comm="mission-control" name="accounts-goa.cfg" dev="sda3" ino=9830641 scontext=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1381425238.577:129): arch=x86_64 syscall=rename success=yes exit=0 a0=1921930 a1=1924e40 a2=3f4abb1768 a3=616f672d73746e75 items=0 ppid=6597 pid=6598 auid=42 uid=42 gid=42 euid=42 suid=42 fsuid=42 egid=42 sgid=42 fsgid=42 ses=1 tty=(none) comm=mission-control exe=/usr/libexec/mission-control-5 subj=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 key=(null) Hash: mission-control,xdm_dbusd_t,xdm_var_lib_t,dir,remove_name audit2allow #============= xdm_dbusd_t ============== allow xdm_dbusd_t xdm_var_lib_t:dir remove_name; allow xdm_dbusd_t xdm_var_lib_t:file { rename unlink }; audit2allow -R require { type xdm_dbusd_t; type xdm_var_lib_t; class dir remove_name; class file { rename unlink }; } #============= xdm_dbusd_t ============== allow xdm_dbusd_t xdm_var_lib_t:dir remove_name; allow xdm_dbusd_t xdm_var_lib_t:file { rename unlink }; # sealert -l 82110924-588f-46f1-b496-d270da8c0bb3 SELinux is preventing /usr/libexec/mission-control-5 from write access on the file user. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that mission-control-5 should be allowed write access on the user 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 mission-control /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 Target Context system_u:object_r:config_home_t:s0 Target Objects user [ file ] Source mission-control Source Path /usr/libexec/mission-control-5 Port <Unknown> Host some.host Source RPM Packages telepathy-mission-control-5.14.0-2.fc18.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-105.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name some.host Platform Linux some.host 3.10.14-100.fc18.x86_64 #1 SMP Fri Oct 4 15:55:52 UTC 2013 x86_64 x86_64 Alert Count 28 First Seen 2013-05-06 09:47:13 MDT Last Seen 2013-10-10 11:13:58 MDT Local ID 82110924-588f-46f1-b496-d270da8c0bb3 Raw Audit Messages type=AVC msg=audit(1381425238.682:132): avc: denied { write } for pid=6598 comm="mission-control" name="user" dev="tmpfs" ino=20452 scontext=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:config_home_t:s0 tclass=file type=SYSCALL msg=audit(1381425238.682:132): arch=x86_64 syscall=open success=yes exit=ENXIO a0=195a5d0 a1=42 a2=180 a3=7ffff72977c0 items=0 ppid=1 pid=6598 auid=42 uid=42 gid=42 euid=42 suid=42 fsuid=42 egid=42 sgid=42 fsgid=42 ses=1 tty=(none) comm=mission-control exe=/usr/libexec/mission-control-5 subj=system_u:system_r:xdm_dbusd_t:s0-s0:c0.c1023 key=(null) Hash: mission-control,xdm_dbusd_t,config_home_t,file,write audit2allow #============= xdm_dbusd_t ============== allow xdm_dbusd_t config_home_t:file write; audit2allow -R require { type xdm_dbusd_t; } #============= xdm_dbusd_t ============== gnome_manage_home_config(xdm_dbusd_t) Version-Release number of selected component (if applicable): telepathy-mission-control-5.14.0-2.fc18 selinux-policy-3.11.1-105.fc18 How reproducible: On every user login Expected results: telepathy-mission-control and selinux cooperate with each other
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.