Description of problem: SELinux is preventing lightdm-gtk-gre from 'setattr' accesses on the directory fontconfig. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow lightdm-gtk-gre to have setattr access on the fontconfig directory Then you need to change the label on fontconfig Do # semanage fcontext -a -t FILE_TYPE 'fontconfig' where FILE_TYPE is one of the following: abrt_var_cache_t, auth_cache_t, auth_home_t, cache_home_t, cgroup_t, config_home_t, data_home_t, dbus_home_t, faillog_t, fonts_cache_t, gconf_home_t, gkeyringd_gnome_home_t, gkeyringd_tmp_t, gnome_home_t, gstreamer_home_t, icc_data_home_t, kdbusfs_t, locale_t, mozilla_plugin_tmp_t, mozilla_plugin_tmpfs_t, pam_var_run_t, user_tmp_t, var_auth_t, xdm_home_t, xdm_log_t, xdm_spool_t, xdm_tmpfs_t, xdm_var_lib_t, xdm_var_run_t, xkb_var_lib_t, xserver_log_t. Then execute: restorecon -v 'fontconfig' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that lightdm-gtk-gre should be allowed setattr access on the fontconfig 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 'lightdm-gtk-gre' --raw | audit2allow -M my-lightdmgtkgre # semodule -X 300 -i my-lightdmgtkgre.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:unlabeled_t:s0 Target Objects fontconfig [ dir ] Source lightdm-gtk-gre Source Path lightdm-gtk-gre Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-225.16.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.11.3-202.fc25.x86_64 #1 SMP Mon Jun 5 16:38:21 UTC 2017 x86_64 x86_64 Alert Count 3 First Seen 2017-06-09 08:32:41 PDT Last Seen 2017-06-09 08:32:41 PDT Local ID 652d5174-be2c-4627-a9f4-b1f107fd5603 Raw Audit Messages type=AVC msg=audit(1497022361.113:155): avc: denied { setattr } for pid=1028 comm="lightdm-gtk-gre" name="fontconfig" dev="sda3" ino=101958156 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=0 Hash: lightdm-gtk-gre,xdm_t,unlabeled_t,dir,setattr Version-Release number of selected component: selinux-policy-3.13.1-225.16.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.3-202.fc25.x86_64 type: libreport
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.