NM fakes a CONNECTED state during resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Due to the patch for bug 191889 in NetworkManager (lp191889_
But this is causing problems for me. After a suspend/resume, NetworkManager sees my deactivated device and treats it as online for a brief moment before it becomes activated again during resume. (I have an attached log from such a suspend/resume.)
So the state sequence as exposed over DBus is something like ASLEEP -> ONLINE (fake) -> DISCONNECTED -> CONNECTING.
But this causes problems for apps that are paying attention to state. For example, Deja Dup watches for when the user is online to know when it can start a backup. And in this situation it says, "oh I'm online, let me do something" and instantly fails.
Is this patch still needed? Can it be smarter? (And at the very least, it should be updated to fake NM_STATE_
Changed in network-manager (Ubuntu): | |
status: | New → Confirmed |
Yup. We still need that patch but there's clearly something wrong there, so
I will investigate.