GNOME Bugzilla – Bug 622362
NetworkManager no longer connects after machine crashed during suspend
Last modified: 2016-03-11 17:42:18 UTC
If a machine crashes during a suspend to disk/ram, after next boot NetworkManager 0.8 will no longer connect to any network (wired or wireless), the applet will always show "networking system disabled". During resume, it wakes up NM by calling dbus_send --system \ --dest=org.freedesktop.NetworkManager \ --print-reply --reply-timeout=200 \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.wake If the machine crashes during suspend, the .wake is not called and NM remains suspended forever. I tracked it down to the fact, that NM apparently remembers the setting in /var/lib/NetworkManager/NetworkManager.state. No matter if it those pm-utils calls are stupid or not, IMHO NetworkManager should not remember this setting via a restart or even a reboot of the machine. Send the .wake or "cnetworkmanager -o true" make it works. But it is only a workaround and not the solution of the problem.
Dan, Is it a good way to resolve this issue? I'd like to patch it, but not have a good idea for it.
It should already be fixed it on 0.8.1 and master. It's because since the 0.6.x days we've used sleep/wake as the "Enable networking" switch. I did some work about a month ago to split that up and add a real enable/disable networking toggle. http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NM_0_8_1&id=ee3ece9dac985034c5c1f81a6769b40fd7856579 and http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=NM_0_8_1&id=30374453b4b12953ed5a9b7bec4b81fe263ae9db should be the 0.8.1 commits for it. *** This bug has been marked as a duplicate of bug 346615 ***