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

[Fabian Greffrath]

I have an update on this bug.

Yesterday I tried to manually grant write access to the rfkill device 
and activate Bluetooth via gnome-bluetooth:

$ sudo chmod 0777 /dev/rfkill
$ bluetooth-properties
** Message: adding killswitch idx 0 state 1
** Message: killswitch 0 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 0 type 2 op 2 soft 0 hard 0

Here the bluetooth-properties window pops up and presents me a big 
button that reads "Activate Bluetooth". I click this button and it 
grays out, though bluetooth is still disabled. The following appears 
on the console again:

** Message: killswitch 0 is 1
** Message: killswitches state 1

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

Fabian

-- 
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax:     +49 (0)234 / 32-14227
E-Mail:  greffrath at leat.ruhr-uni-bochum.de