Ubuntu
gnome-bluetooth package

  1. Bug #2033324
  2. Comment #2

Comment 2 for bug 2033324

Revision history for this message
Christian Pernegger (fallenguru) wrote (last edit ):

Found the cause:

gsd-rfkill[2049]: Could not open rfkill device: Could not open RFKILL control device, please verify your installation

GNOME's BT GUI needs access to /dev/rfkill to work. It's tagged "uaccess" in udev, so in theory all logged-in users should get access via an ACL, but in practice this doesn't seem to work for seats other than seat0 in a multiseat scenario.

Removing the "seat" tag and re-adding the "shared" tag via custom udev rule doesn't help--the acl doesn't get added if you don't login on seat0.

Of course simply changing the permissions to 666 and starting /usr/libexec/gsd-rfkill manually does the trick until the next reboot, but ...

So, not a gnome-bluetooth* bug, nor a gnome-control-center one, but whose is it? Logind? /dev/rfkill should be available to all users logged in locally, IMHO.