dx-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: indicator-bluetooth (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1605330

Title:
  Guarantee access to /dev/rfkill

Status in indicator-bluetooth package in Ubuntu:
  New

Bug description:
  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).

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