Comment 30 for bug 524454

Running Lucid Kubuntu here. Fully up to date and I can report that it is still occurring for me as well. All I've come up with is that if I attempt to hibernate or suspend to ram (both fail in Lucid both worked in Karmic, this install is a clean install as I wanted to re-partition. )

If I either write a script in rc.local that sed's the NetworkManager.state file on startup to change false to true, or if I use the chattr command and set the immutable bit (chattr +i so that not even root can modify the file.) it doesn't have this problem after a suspend crash/failure occurs. However if I don't do this every time suspend of any kind crashes or fails I have this problem occur.

What appears to happen is that normal suspend should write this state info out to this file so that the system doesn't react to commands while suspended. (Like wake-on-lan?) then it should write back to the file upon return from suspend to re-enable connectivity. This also seems to have the added advantage of dealing with cases where you suspend with wireless at location A and resume with wireless or wired at location B. You don't end up with the iPad problem (this is good.)

The solution seems to be giving knetworkmanager or the gnome equivalent a button to "Enable Network Management" Conversely a button to disable it would also be a nice feature. In other words I don't think the bug is with the code as it exists, I think the bug is a missing feature (ie the Enable button)