Comment 100 for bug 1252121

So I patched pm-suspend to exit 0, and that would not trigger the bug anymore.

I added a sleep as you suggested and NM would disconnect and then reconnect up to sleep value of 25 but not with sleep values of at least 26. I think we're looking at a 30 seconds timeout since my system takes some seconds to settle from the suspend code pathes (keyboard and display backlights take a couple of seconds to get turned off).

The failing case also differs from the working case in that the screen doesn't turn back on; I guess this is because the signal which we're missing for Network Manager also misses for gnome-screensaver.