Comment 15 for bug 1386109

At this point there is not much to do: the device is getting removed and NM sees only the state change to unmanaged, since we're dealing with hybris-only devices in this particular case: this wouldn't happen with a traditional rfkill device. There's also other code that deals with unmanaged devices to let NM be online in that case, since that's important on desktops which may have network devices configured manually, outside of NetworkManager.

I'm going to try forcing a state update at the end of the urfkill state change handlers, see if that is sufficient as a workaround, but past that there won't be another place to hook into in order to update states.

Moreover, the connectivity API/indicator-network should be requesting a new state from NetworkManager when it gets asked for the state of the system, even if it's receiving the signals. This call always causes NM to re-check its internal state.