GNOME Bugzilla – Bug 742675
[PATCH] core: ensure manager state is updated on resume with connectivity checking enabled
Last modified: 2015-02-25 14:09:02 UTC
On resume configured interfaces are unmanaged to clear their pre-resume state and then re-managed. Eventually the interface should end up moving to the DISCONNECTED state, which should trigger an auto-activate check in the Policy. If connectivity checking was enabled, that auto-activate check would fail because the Manager's state was still NM_STATE_ASLEEP. This caused bridge slaves not to auto-activate on resume, which left bridges without connectivity. The manager never left NM_STATE_ASLEEP when connectivity checking was enabled due to nm_manager_update_state() returning early when kicking off a connectivity check. Instead, the manager's state should always be updated to accurately reflect the current state.
Created attachment 294187 [details] [review] 0001-core-ensure-manager-state-is-updated-on-resume-with-.patch
Comment on attachment 294187 [details] [review] 0001-core-ensure-manager-state-is-updated-on-resume-with-.patch so I'm the one who suggested this approach, so I don't know if my review counts, but looks good to me! :)
LGTM too (didn't test it)
*** Bug 741687 has been marked as a duplicate of this bug. ***
master: a687d1f9e0f75b987f40335934b54aa748f6724b nm-1-0: cd26f835f4dd2286bd73fed3e7236d17ea147920 nm-0-9-10: a5a7e5cbaaa36d6e1f346e5349a15d8b3a36e10a