[Bug 2033324] Re: no adapter found on second seat [loginctl multiseat]

[Christian Pernegger]

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 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.

-- 
You received this bug notification because you are a member of
Bluetooth, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/2033324

Title:
  no adapter found on second seat [loginctl multiseat]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/2033324/+subscriptions