Bug#552185: gnome-bluetooth] read/write access to the /dev/rfkill device is required

Andrea Veri andrea.veri89 at gmail.com
Fri Dec 18 23:43:12 UTC 2009


On Wed, 09 Dec 2009, Fabian Greffrath wrote:

> Looks like it's a regression in bluez and not gnome-bluetooth's
> fault. What do you think?

Well, the real problem here is that bluez lacks its own rfkill, so users
are stuck when trying to enable / disable their bluetooth interfaces.

While we could patch gnome-bluetooth to provide this kind of access, I am
still trying to find out what's the best way to workaround this since the Ubuntu
way has been rejected upstream. (I guess you know that giving rfkill access by default
to normal users is not the best to do at the moment)

Looking at the informations you just provide, the issue seems to be in bluez itself,
I think that you should forward the results of your tests directly upstream so we can
start having an idea of what's going on.

Upstream's Mailing Lists details can be found at this page:

http://www.bluez.org/development/lists/

please report back here if you have any update, so let's keep this bug as the main thread for 
this discussion.

Thanks in advance,

Andrea
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20091219/1504d78d/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list