If a snapshot cycle via Suspend to RAM, userspace software suspend, whatever does not work out, Network Manager stays disabled until one changes it manually.

Use case:

- Someone suspend his laptop. At least on Debian /usr/lib/pm-utils/sleep.d/55NetworkManager is started when pm-utils is used. It sends a dbus message:

 11 suspend_nm()
 12 {
 13 »·······# Tell NetworkManager to shut down networking
 14 »·······dbus_send --print-reply --system                         \
 15 »·······»·······--dest=org.freedesktop.NetworkManager  \
 16 »·······»·······/org/freedesktop/NetworkManager        \
 17 »·······»·······org.freedesktop.NetworkManager.sleep 2>&1 > /dev/null
 18 }

- Resume does not work as expected. The user fully boots the machine instead

- Network Manager stays enabled, it does not reset its state.

Thus the user needs to wake Network Manager by hand even tough the machine is fully up and running. This is especially annoying for users of the KDE network manager applet, since this doesn't provide a function to wake Network Manager.

For days I stopped Network Manager and just used dhclient on the interface, but then Network Manager aware application get fooled to think that the network is not online.

Today I had enough of it, googled and found: http://bugs.debian.org/566891

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

from message 10 aka http://bugs.debian.org/566891#10 did the trick for me.

dbus_send command was not found.

Expected results:

After a fresh reboot Network Manager is fully up and running.

Versions in use:

martin@shambhala:~> apt-show-versions | egrep "(network-manager|pm-utils)"
network-manager/squeeze uptodate 0.8-1
network-manager-gnome/squeeze uptodate 0.8-1
network-manager-kde/squeeze uptodate 1:0.9~svn1125524-1
network-manager-openvpn/squeeze uptodate 0.8-1
network-manager-pptp/squeeze uptodate 0.8-2
network-manager-vpnc/squeeze uptodate 0.8-1
pm-utils/squeeze uptodate 1.3.0-1