Jul 13 14:30:23 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:23 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:23 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:23 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:23 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:23 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:23 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:23 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:23 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:23 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:30:24 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:30:24 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:48 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:48 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:49 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:49 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:49 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:49 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:49 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:49 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:49 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:49 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:49 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:49 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:39:50 fedora26 setroubleshoot: SELinux is preventing gsd-xsettings from setattr access on the directory cache. For complete SELinux messages run: sealert -l 11e85912-b10c-40bd-aed7-2b5733d8d130
Jul 13 14:39:50 fedora26 python3: SELinux is preventing gsd-xsettings from setattr access on the directory cache.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gsd-xsettings should be allowed setattr access on the cache directory by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gsd-xsettings' --raw | audit2allow -M my-gsdxsettings#012# semodule -X 300 -i my-gsdxsettings.pp#012
Jul 13 14:43:22 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:43:22 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:43:22 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:43:22 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:43:22 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:43:22 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:43:22 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:43:22 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:43:25 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:43:25 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:47:49 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:47:49 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:47:49 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:47:50 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:47:50 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:47:50 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:47:50 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:47:50 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 14:47:52 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 14:47:52 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 15:00:35 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 15:00:35 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 15:00:36 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 15:00:36 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 15:00:36 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 15:00:36 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 15:00:36 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 15:00:36 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012
Jul 13 15:00:38 fedora26 setroubleshoot: SELinux is preventing gnome-shell from read access on the lnk_file machine-id. For complete SELinux messages run: sealert -l c785751e-5531-4fd6-93e9-516da71dc063
Jul 13 15:00:38 fedora26 python3: SELinux is preventing gnome-shell from read access on the lnk_file machine-id.#012#012*****  Plugin catchall (100. confidence) suggests   **************************#012#012If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell#012# semodule -X 300 -i my-gnomeshell.pp#012