Comment 103 for bug 1286552

I see it on a laptop that does not connect automatically to the wireless network after wakeup. But I have the same issue also with a desktop with wired ethernet. So a more appropriate title would be 'network manager fails to reconnect after resume', because the issue is not wifi specific.

After a suspend/resume cycle, network manager does not reconnect.

For the desktop, given that this used to be a machine going to sleep when unused and being waken from the lan, the issue is pretty bad. The machine wakes... but with no network. Network manager stays there for ever, with the connection ready and selected for automatic connection, but does not even try to start the connection.

Since it completely breaks the usability of wol, please rise priority.

This is something recent. I have also started to see it about November. Furthermore, it used to work just fine with 14.04.