Comment 22 for bug 446657

@Baptiste: please read the full bug history. This bug was initially reported against gnome-bluetooth, forwarded upstream, rejected, then moved against bluez, forwarded upstream, and confirmed non-existent there. This turns out to be an Ubuntu-specific problem that prevents bluez from using its existing feature of loading the previously recorded on/off state, which is caused by a dbus communication issue or, most likely, inaction on the dbus communication between gnome-bluetooth and bluetoothd.

The bug title is correct and the comments are on-topic. The only messiness stems from the fact that this bug has required reporting to two different upstreams to discover the nature of the problem, but that's just the way things have panned out.

Please reconsider whether you really wish to move the bug against bluez again.