Blueman RfKill State
Posted: 2018-08-06 Filed under: system | Tags: blueman, bluetooth, lp, netdev, polkit, rfkill 3 CommentsI made a clean install of Slackware64 14.2 on my laptop. I updated the system to the latest patches and when I logged in to Xfce I was presented with a weird dialogue window. Apparently it belongs to Blueman, telling me that “Setting RfKill State requires privileges”. Even when I enter my password, it would appear again upon every log in. Very annoying. However, the solution was recently discussed at LQ.
So, let’s get rid of this:
Following the instructions in post 12 by Skaendo, I created a file called 10-blueman.rules
with the following contents:
/* Allow users in netdev group to use blueman feature requiring root without authentication */ polkit.addRule(function(action, subject) { if ((action.id == "org.blueman.network.setup" || action.id == "org.blueman.dhcp.client" || action.id == "org.blueman.rfkill.setstate" || action.id == "org.blueman.pppd.pppconnect") && subject.isInGroup("netdev")) { return polkit.Result.YES; } });
I placed it in /etc/polkit-1/rules.d/
and now the annoying dialogue is gone. My user is member of the lp
and netdev
groups. So far things seem to work fine, but I will follow the LQ thread and Slackware’s ChangeLog for further development on the topic. Maybe the issue will be fixed in -current (and -stable) pretty soon?
We are now in 2021, I’m using Slackware current and the rfkill’s dialogue window problem seems to got back!
I am using a bit ‘older’ -current (installed from 05 January), so I have not encountered problems. Maybe you can post on Slackware’s forum at LQ?
You can also arrange to NOT have rfkill called on session start.
Ya know ~/.config/autostart? There is another directory like that, which applies to all users: /etc/xdg/autostart. If there is a blueman.desktop in that directory, it is invoking rfkill.
I removed that file.