Comment # 10 on bug 1227344 from Alice Brooks

Hmm it's a difficult one. If you look at it from a systems management point of
view, the correct behavior is to not show it on a system that doesn't have
Selinux enabled. Since what are you going to be managing there

I've double checked and if you network two systems, one with Selinux and one
without, this behavior works fine. Selinux is shown on the system that does
have it while on the original system it is hidden since Selinux is disabled or
not installed

I don't think a message in the style of Podman's "Service not running" would
work particularly well, since Podman's is easily recoverable. Whereas Selinux's
setup can be a lot more specific system wise and a bit more hands on. I'd
suggest adding a message against the application in the apps screen however, a
little note specifying that it's not in use for this system as Selinux is not
enabled potentially with a link to the distributions documentation. That way it
could also easily cover other apps that find themself in a similar position,
this would require cockpit-packagekit to be installed however

I'm open to thoughts on my proposal