http://bugzilla.novell.com/show_bug.cgi?id=585433 http://bugzilla.novell.com/show_bug.cgi?id=585433#c0 Summary: NetworkManager 0.8 no longer connects after machine crashed during suspend Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: tambet@novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: hmacht@novell.com, vbotka@novell.com, rjw@novell.com Found By: Community User Blocker: --- 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". I tracked it down to the fact, that NM since 0.8 apparently remembers the "suspended" setting over a restart / reboot. During suspend, pm-utils calls dbus-send --system \ --print-reply --reply-timeout=200 \ --dest=org.freedesktop.NetworkManager \ /org/freedesktop/NetworkManager \ org.freedesktop.NetworkManager.sleep 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. 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. (adding people to CC who will probably have to deal with fallout from this bug, because it might get attributed to suspend or wireless). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.