Blue man on non admin account.

[Biotud]

Hi

I've set up a non admin account for my kids in Ultramarine 42 (Fedora) and if they want to enable Bluetooth, it asks for admin password (rfkill). The only way I currently has fixed it is to add the account to "wheel" which is not optimal.

Is there any way to fix this without adding the account to wheel?

[cschramm]

I see two options:

1. You can configure custom polkit rules to allow the org.blueman.rfkill.setstate action, e.g., to everyone or specific users or groups. See https://github.com/blueman-project/blueman/wiki/PolicyKit. Most probably, your distribution configures exactly what the example shows.
2. Disable the KillSwitch plugin. blueman will not try to change the kill switch state when the power state changes then. The user can still toggle the power state and things will work as long as the kill switch is not set.

[Biotud]

Thx, I'm new to Linux (3 months in), I just changed the group from "wheel" to "users" in the policy rule as I really don't want my kids in the wheel group.