I’m running RoonServer on fedora and it generates a ton of SELinux alerts. especially RAATServer to controlC0. How do I make it stop? I don’t think that it should access controlC0 when someone is logged it, but that’s just a guess.
If you’re running a desktop, open SELinux Alert Browser and this will help you to solve the alerts.
Thanks! Now what?
I use Ubuntu, so don’t need to deal with SELinux, so this was simply a pointer. The browser helps you to understand the alerts, and if appropriate, create a policy to allow the activity, i.e. prevent further alerts.
I just Googled this: https://hk.saowen.com/a/939ecc8bc457182d81b7c721f7a9cc1088f02efbe85fb44883d791b137fba9ea.
You need to either add a policy rule to SELinux, disable SELinux at boot*, or use Ubuntu (which doesn’t use SELinux.)
*Know the implications of doing this for you server.
Sorry but that’s not a fix
Those are your options.
I, like @Martin_Webster, am an Ubuntu user. So I don’t experience this problem.
In your first post you said that you didn’t think the RAATServer should have access to ControlC0 but that you weren’t sure.
Since Roon uses ALSA (Advanced Linux Sound Architecture) and ALSA uses ControlC0, why is allowing it access a problem? This question is rhetorical because I don’t know the answer. I’m simply prompting you to reevaluate your original assumption. If you decide that it’s probably okay, then the alert you posted gave a command to run to allow this access and the alerts should go away.
Below is a line from O’Reilly’s Fedora Linux book that made me think allowing access may not be that problematic:
1 Like