I’m using a Lenovo Thinkpad Yoga 260 (Skylake), running Tumbleweed (original installation was of Gnome Desktop, but I’m currently using Cinnamon).
The toggle in the Bluetooth applet to enable/disable the Bluetooth radio does not work, and running rfkill brings up a message saying that running as root may be required.
I followed the instructions in this thread to create a new udev rule, but for whatever reason rfkill permissions still don’t change.
I eventually gave up and created a systemd service that runs a shell script to chmod a+x /dev/rfkill at startup. Was wondering if there’s any further documentation on this issue before I post to Bugzilla.
> I followed the instructions in ‘this thread’
> (http://tinyurl.com/y8jovw3a) to create a new udev rule, but for
> whatever reason rfkill permissions still don’t change.
Well, that thread is 7 years old and udev syntax has changed regularly through
time.
Try something like this:
KERNEL==“rfkill”, MODE=“0666”
or if you want to restrict it so some group (even one you might create for that
taks).
KERNEL==“rfkill”, MODE=“0664”, GROUP=“GROUPNAME”
and add yourself to that group (maybe create a group called “bluetooth” or
“rfkill” ans use that as GROUPNAME.)
AK
–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)
Although I actually did suggest this as one possible option, I also have to add that this is of course very (too?) permissive (=everybody can switch RFkill on/off). Using an extra group (= my second suggestion) is way more secure (and the one I prefer on my systems).
To the best of my knowledge that seems to be true (on both accounts, useless but harmless).