The scenario in comment #2 isn't valid. That said, I am able to reproduce by killing NetworkManager, so I agree this is a valid bug that needs to be fixed.
@Pat
As Alfonso pointed out, your problem is different, as there's no active context, nor does NetworkManager appear stuck. Could you please file a new bug, and if possible nail down the exact steps to reproduce? As described, it sounds like an indicator bug.
@Alfonso
The scenario in comment #2 isn't valid. That said, I am able to reproduce by killing NetworkManager, so I agree this is a valid bug that needs to be fixed.
@Pat
As Alfonso pointed out, your problem is different, as there's no active context, nor does NetworkManager appear stuck. Could you please file a new bug, and if possible nail down the exact steps to reproduce? As described, it sounds like an indicator bug.