Follow-up on the lost network of resume

[Julien Olivier]

Hi list,
 some days ago I wrote an email to this same list about lost network
after resume.

I have since reported a bug, but go absolutely no feedback:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1187005

Now, it seems I have finally found the culprit, even if I'm not sure I
understand everything. According to this entry in pm-utils' changelog,
it seems that network-manager doesn't handle 'suspend' / 'wake' calls
correctly, and this might be the reason why network-manager stops
working after resuming from suspend.

pm-utils (1.4.1-9git1) raring; urgency=low

  Upload current Debian packaging git head.

  * debian/rules: Stop installing sleep.d/55NetworkManager. Current
    NetworkManager does not even expose this API any more, so the
    sleep()/wake() calls just always fail. As NM is apparently able to
deal
    with suspends just fine, no need to waste cycles on this.

I'm writing to the list because this is a pretty annoying bug and I am
just trying to get more attention to it than I got from the bug report.
Sorry if this is not appropriate.

Thanks!