Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

akspecs · 2019-04-02 09:08:10

Hello, I hope we're all doing well.

After a recent system upgrade, I noticed that I am unable to toggle my bluetooth via the blueberry UI. In my case, when attempting to toggle from on to off I get:

rfkill: cannot open /dev/rfkill: Permission denied

I was able to downgrade gnome-bluetooth from 3.32.1-1 to 3.32.0-1 and I am able to toggle bluetooth via the UI again.

I'm curious if anyone else has run into this issue, as prior to the upgrade I don't ever recall having permission issues. Also, the downgraded version of gnome-bluetooth with blueberry appears to freeze and not respond when toggling bluetooth, requiring to force quit the ui.

If I'm not the only one experiencing this, I'd be willing to file (another) bug report. At first glance I can't tell if it's blueberry that needs to be updated to incorporate changes with gnome-bluetooth, or if gnome-bluetooth is solely to blame. Here's the gnome-bluetooth commit page. Here's another user describing this issue a couple months ago on mint's blueberry github

bugsmanagement · 2019-04-03 12:01:35

Hey akspecs,

akspecs wrote:

After a recent system upgrade, I noticed that I am unable to toggle my bluetooth via the blueberry UI. In my case, when attempting to toggle from on to off I get:

I don't have bluetooth here but have you narrow that to what package? system upgrade is too vague?

Cheers

akspecs · 2019-04-05 05:21:06

bugsmanagement wrote:

. . . have you narrow that to what package? system upgrade is too vague? . . .

akspecs wrote:

downgrade gnome-bluetooth from 3.32.1-1 to 3.32.0-1 and I am able to toggle bluetooth via the UI again.

There's some sort of an incompatibility with the new gnome-bluetooth and blueberry is what I've managed to narrow it down to. I'm running the cinnamon de as well, so it would seem everyone else who uses cinnamon + blueberry as a ui for their bluetooth should be experiencing this as well.

seth · 2019-04-05 06:49:43

It probably dropped some suid/guid, try adding yourself to the rfkill group.

akspecs · 2019-04-05 09:06:27

seth wrote:

It probably dropped some suid/guid, try adding yourself to the rfkill group.

Undoubtedly that works, but does that mean every user who wants to be able to toggle on/off their bluetooth devices will need to be a part of the rfkill group? That's new...

seth · 2019-04-05 11:17:10

That's not new.
The /dev/rfkill permissions have been that ever since ("I can remember") and /bin/rfkill has no suid/guid so you'd always have to sudo that (or get yourself into the rfkill group)
Afaics there's also no systemd ACL handling for the active user.

What probably caused the change is https://git.archlinux.org/svntogit/pack … c1c5b1a85b ?

Arch Linux

#1 2019-04-02 09:08:10

Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

#2 2019-04-03 12:01:35

Re: Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

#3 2019-04-05 05:21:06

Re: Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

#4 2019-04-05 06:49:43

Re: Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

#5 2019-04-05 09:06:27

Re: Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

#6 2019-04-05 11:17:10

Re: Bluetooth issues - rfkill: cannot open /dev/rfkill: Permission denied

Board footer