However, if I unpower the device using the Kubuntu applet (it's relaibly not working, draining 5 Watts less)
/etc/init/rfkill-store
will save the state as enabled
/var/rfkill/saved-state
contains
hci0 0
after a boot. So it seems the device remembers it's last state and not bluetoothd. With the hardware lit always on, I suspect it is a hardware issue with my adapter rather than an error with upstart or bluetoothd.
However, if I unpower the device using the Kubuntu applet (it's relaibly not working, draining 5 Watts less)
/etc/init/ rfkill- store
will save the state as enabled
/var/rfkill/ saved-state
contains
hci0 0
after a boot. So it seems the device remembers it's last state and not bluetoothd. With the hardware lit always on, I suspect it is a hardware issue with my adapter rather than an error with upstart or bluetoothd.