http://bugzilla.novell.com/show_bug.cgi?id=585433 http://bugzilla.novell.com/show_bug.cgi?id=585433#c14 Will Stephenson <wstephenson@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|wstephenson@novell.com |bili@novell.com Summary|KNetworkManager 0.8 no |NetworkManager 0.8 no |longer connects after |longer connects after |machine crashed during |machine crashed during |suspend |suspend Severity|Major |Critical --- Comment #14 from Will Stephenson <wstephenson@novell.com> 2010-06-18 10:36:01 UTC --- Bin Li, While it's true that knetworkmanager needs an 'enable networking' action, this bug is about the daemon not clearing its 'sleep' state on normal boot after a failed suspend, and using a client to manually wake networkmanager is a workaround. Consider the case where you turn on a machine, not knowing that its last suspend failed, and NM is asleep until someone logs in and wakes it - no networking, not even system connections. As per comment #2 and #5, NM should check if the startup follows a failed suspend and clear any persisted state. Back to you :) -- 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.