Comment 72 for bug 524454

The fact that this happens on a failed suspend/resume indicated it's not NetworkManager's fault, but that the issue resides in the scripts run to "suspend" networking on S3/S4 states.

I'm assigning myself for the tasks for both Lucid and Maverick, there needs to be some work done to see if the commits fa70542c618665cf203a2b71fa0e504f759f7902 in NM and adf56461a7859280f8ea1520c9689e9383fab3f6 in nm-applet can be directly applied or backported; I'll make a test package available in a PPA (or -proposed).