Bluetooth cannot be switched on/off on Nexus 4 (rfkill issues)

[Łukasz Zemczak]

When using the latest indicator-bluetooth on the Nexus 4 (mako) and Ubuntu Touch switching bluetooth on/off is impossible, as the state never changes. Same when doing it from the ubuntu-system-settings.

The unity8.log upstart log has this in it:
Can't open /dev/rfkill for use as a killswitch backend: Permission denied
Couldn't write rfkill event: Bad file descriptor
Can't open /dev/rfkill for use as a killswitch backend: Permission denied

[Impact]
 * User has no chance to switch bluetooth on or off which can also pose a security problem when having bluetooth on all the time.

[Test Case]
 * Try to switch BT on/off via indicator or system settings.

[Regression Potential]
 * None really as it cannot be more broken as it is currently.

[Charles Kerr (charlesk)]

This is a permissions issue with /dev/rfkill. If indicator-bluetooth can't read or write /dev/rfkill, it can't toggle bluetooth on & off.

[Oliver Grawert (ogra)]

i made /dev/rfkill owned by the android_input group several weeks ago (when you pinged me on IRC about it)
the group has rw permissions and is teh default group of the phablet user, as long as your process is started by this user it should work. i can not really make it world writable (0666)

[Oliver Grawert (ogra)]

so playing with the UI switch it seems to work fine here:

root@ubuntu-phablet:/# rfkill list all
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no
root@ubuntu-phablet:/# rfkill list all
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

(toggling it crashes unity8 but the toggle definitely blocks/unblocks fine)

[Charles Kerr (charlesk)]

This bug has the same fix as bug #1236249, so the MPs there will resolve this.

I would mark this as a duplicate ticket, but I'm feeling pedantic and these actually are two separate bugs with the same fix...

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:indicator-bluetooth at revision 70, scheduled for release in indicator-bluetooth, milestone Unknown

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-bluetooth - 0.0.6+13.10.20131016-0ubuntu1

---------------
indicator-bluetooth (0.0.6+13.10.20131016-0ubuntu1) saucy; urgency=low

  [ Charles Kerr ]
  * When the user chooses to toggle bluetooth on or off, if /dev/rfkill
    isn't available, fall back to toggling org.bluez.Adapter's Powered
    property. (LP: #1236249, #1230275)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 70
 -- Ubuntu daily release <email address hidden> Wed, 16 Oct 2013 02:34:31 +0000