Guarantee access to /dev/rfkill

[Michael Terry]

indicator-bluetooth wants direct access to /dev/rfkill.

In Ubuntu, that access is granted to the current active user by logind by virtue of the uaccess tag on /dev/rfkill.

That tag is granted by /lib/udev/rules.d/61-gnome-settings-daemon-rfkill.rules from the gnome-settings-daemon package.

I think indicator-bluetooth either should:

1) ship its own version of that file to grant the uaccess tag to /dev/rfkill, or

2) simply use the DBus api provided by rfkilld, if that's possible (I don't happen to know whether indicator-bluetooth's rfkill usage can be easily ported)

This came up in the context of Ubuntu Touch, where gnome-settings-daemon is not installed (the phablet user is granted access by being in the android_input group, but that is a solution we'd like to move away from as we support more users and a proper lightdm greeter).

[Michael Terry (mterry)]

Note that on current Touch phones, only the mako has a kernel with uaccess (ACL) support built in. So if you go that route and want to test on Touch, use a mako.