Comment 4 for bug 907818

On second thought, the last event is not cleanup, since it is recognizing the switch as _on_ for idx{0,1}. It looks like the device might have to be initialized first before it sends the signal that the rfkill switch has been turned on. Here is more complete what's going on before that:

bluetoothd[1982]: Adapter /org/bluez/1982/hci0 has been enabled
bluetoothd[1982]: plugins/hciops.c:hciops_set_discoverable() hci0 discoverable 0
bluetoothd[1982]: plugins/hciops.c:hciops_set_pairable() hci0 pairable 1
bluetoothd[1982]: src/adapter.c:btd_adapter_unref() 0x7fc70e13b6b0: ref=6
bluetoothd[1982]: plugins/hciops.c:child_exit() child 1998 exited
bluetoothd[1982]: src/adapter.c:register_agent() Agent registered for hci0 at :1.39:/org/bluez/agent/hci0
bluetoothd[1982]: plugins/hciops.c:read_tx_power_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: plugins/hciops.c:read_local_name_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: plugins/hciops.c:read_simple_pairing_mode_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: plugins/hciops.c:read_local_name_complete() hci0 status 0
bluetoothd[1982]: plugins/hciops.c:update_ext_inquiry_response() hci0
bluetoothd[1982]: plugins/hciops.c:read_scan_complete() hci0 status 0
bluetoothd[1982]: src/adapter.c:adapter_mode_changed() old 0x00 new 0x02
bluetoothd[1982]: src/adapter.c:adapter_set_limited_discoverable() FALSE
bluetoothd[1982]: plugins/hciops.c:hciops_set_limited_discoverable() hci0 limited 0
bluetoothd[1982]: src/adapter.c:set_mode_complete()
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 2 soft 0 hard 0
bluetoothd[1982]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 2 soft 0 hard 0