Further the audit log that you pretty much always need to consult when something fails for mysterious reasons in case it might be SELinux isn’t even readable by the user that got dinged. So I can’t even code in a way to check if SELinux was the reason and guide the user, instead I have to provide a diagnostic utility they have to ‘sudo’ to explain to them, or be vague and say 'check if selinux is somehow involved. So I end up despite doing my damndest to not run with privilege asking users to run something with privilege to check a security mechanism.
fedora preinstalls a tool that warns users if they have tripped up in selinux, and provides dome details
fedora preinstalls a tool that warns users if they have tripped up in selinux, and provides dome details
alerts are shown to the user in desktop notifications, and there’s a gui tool with some actions