Description of problem: When I installed the google-roboto-fonts-2.136-2.fc26.noarch.rpm package from the heikoada / gtk-themes copr, SELinux Troubleshooter opened up with an alert that SELinux is preventing gsd-xsettings from 'setattr' accesses on the directory /usr/lib/fontconfig/cache. Version-Release number of selected component (if applicable): selinux-policy-3.13.1-259.fc26 How reproducible: This has been happening off and on, but I haven't been paying much attention to what triggers it. Installing the package I mentioned seemed to do it this time.
SELinux is preventing gsd-xsettings from 'setattr' accesses on the directory /usr/lib/fontconfig/cache. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gsd-xsettings should be allowed setattr access on the cache 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: # ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings # semodule -X 300 -i my-gsdxsettings.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:lib_t:s0 Target Objects /usr/lib/fontconfig/cache [ dir ] Source gsd-xsettings Source Path gsd-xsettings Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages fontconfig-2.12.1-4.fc26.i686 fontconfig-2.12.1-4.fc26.x86_64 Policy RPM selinux-policy-3.13.1-259.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.11.7-300.fc26.x86_64 #1 SMP Mon Jun 26 14:54:05 UTC 2017 x86_64 x86_64 Alert Count 12 First Seen 2017-06-26 02:01:40 CDT Last Seen 2017-06-26 22:23:57 CDT Local ID 89a57f3d-48fc-41d7-9ab6-c162aeb36878 Raw Audit Messages type=AVC msg=audit(1498533837.243:378): avc: denied { setattr } for pid=1319 comm="gsd-housekeepin" name="cache" dev="dm-0" ino=1839351 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:lib_t:s0 tclass=dir permissive=0 Hash: gsd-xsettings,xdm_t,lib_t,dir,setattr
Experiencing identical error in my F26: SELinux is preventing gsd-xsettings from setattr access on the directory /usr/lib/fontconfig/cache. ***** Plugin catchall (100. confidence) suggests ************************** If sie denken, dass es gsd-xsettings standardmäßig erlaubt sein sollte, setattr Zugriff auf cache directory zu erhalten. Then sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Do allow this access for now by executing: # ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings # semodule -X 300 -i my-gsdxsettings.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:lib_t:s0 Target Objects /usr/lib/fontconfig/cache [ dir ] Source gsd-xsettings Source Path gsd-xsettings Port <Unbekannt> Host madrid.waterbeach.solosade.com Source RPM Packages Target RPM Packages fontconfig-2.12.1-4.fc26.x86_64 fontconfig-2.12.1-4.fc26.i686 Policy RPM selinux-policy-3.13.1-259.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name madrid.waterbeach.solosade.com Platform Linux madrid.waterbeach.solosade.com 4.11.8-300.fc26.x86_64 #1 SMP Thu Jun 29 20:09:48 UTC 2017 x86_64 x86_64 Alert Count 11 First Seen 2017-07-05 23:39:49 CEST Last Seen 2017-07-16 09:39:17 CEST Local ID e40d1a85-afa0-4899-b207-4eba29cdac57 Raw Audit Messages type=AVC msg=audit(1500190757.457:261): avc: denied { setattr } for pid=1684 comm="gsd-xsettings" name="cache" dev="dm-0" ino=1835369 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:lib_t:s0 tclass=dir permissive=0 Hash: gsd-xsettings,xdm_t,lib_t,dir,setattr
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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 this bug is closed as described in the policy above. 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.