NM fakes a CONNECTED state during resume

[Michael Terry]

Due to the patch for bug 191889 in NetworkManager (lp191889_always_offline_with_unmanaged_devices.patch), unmanaged devices are treated as online.

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_CONNECTED_GLOBAL instead of NM_STATE_CONNECTED.)

[Mathieu Trudel-Lapierre (cyphermox)]

Yup. We still need that patch but there's clearly something wrong there, so
I will investigate.

[Mathieu Trudel-Lapierre (cyphermox)]

Note the states NM_STATE_CONNECTED_GLOBAL and NM_STATE_CONNECTED are essentially the same. Work is still needed to revise that patch but I think it also needs work at the application level to check how available the network is before trying to do stuff.

I'll need to know more about what's going on before I can fix anything. Could you reproduce the issue and attach all of /var/log/syslog, and probably include the error message from DejaDup or let me know roughly where in the code this is happening?

[Hernando Torque (htorque)]

I cannot reproduce this anymore. I have no issues when resuming from standby.