NM comes up from suspend with state CONNECTED

[Johannes Rudolph]

Binary package hint: network-manager

Since the change introduced for #191889, NetworkManager comes up from suspend or hibernate with state CONNECTED. This is sent to DBus as well. This is a problem since all the interfaces are down yet.

It makes subscribers to NetworkManager.StateChanged report spurious errors if they expect the network to be available. This applies to IMs like pidgin or synapse but probably to other apps as well.

wrt #191889, the question is why NM thinks interfaces are not managed, if in fact they were managed before suspend. Shouldn't they be remembered from before going to sleep?

[Johannes Rudolph (johannes-rudolph)]

Why do you think it does not affect synapse? Here's the bug ticket I filed at the synapse bug tracker:
http://firerabbit.lighthouseapp.com/projects/23238/tickets/68-be-aware-of-internet-connection-state

[Pedro Villavicencio (pedro)]

that's not the right way to open a task for that. I'll do it for you now.

[Pedro Villavicencio (pedro)]

ok so: on the synapse side, there's no package published for ubuntu and the "upstream" product created here doesn't have any report nor subscribers not even a bug triager, so makes no sense to leave a task open that nobody is ever going to see. Moreover that's not a bug on NM rather on the apps, so please open bugs there. If you're not agreed with the change made on the bug you mentioned, please comment that there, there's no need to open a new report to just say that. thanks.