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

[Andrea Veri]

2010/1/5 Fabian Greffrath <fabian at greffrath.com>

> Update: I tried at home with all different combinations of bluez
> packages (the current ones from Debian unstable and the ones from the
> Debian backports) and gnome-bluetooth (also the current ones from Debian
> unstable and the current ones from Ubuntu) - both with /dev/rfkill
> permissions manually set to 777 and left untouched - and *nothing*
> works.
>


I don't think this issue is bluez-related, since it appeared for the very
first time when we upgraded to gnome-bluetooth's 2.28.x series.

I gave a look at gnome-bluetooth's git logs and I found out some interesting
pieces of code you might want to have a look at:

http://git.gnome.org/browse/gnome-bluetooth/commit/?id=822c0ba3d02183cbac571dcc01f1b234d355c851
and
http://git.gnome.org/browse/gnome-bluetooth/commit/?id=3d2fb9c86dabc35193228948bcb0e6813412f9d5

this means that every g-bluetooth's release *after* the 2.27.9 one will have
this issue, so downgrading to a release which is before that one would fix
this issue.

Did you try the Ubuntu package with bad results as well? they added the udev
rule that should fix this rfkill issue, so it looks to me a bit strange that
nothing works even with it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20100106/398ce8da/attachment-0001.htm>