I've just found this entry in pm-utils' changelog:
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 guess that systemd-logind sends the "sleep" signal to network-manager, but network-manager never sends back the "wake" signal. So, the solution would be to just stop sending the "sleep" signal to network-manager on suspend.
I've just found this entry in pm-utils' changelog:
pm-utils (1.4.1-9git1) raring; urgency=low
Upload current Debian packaging git head.
* debian/rules: Stop installing sleep.d/ 55NetworkManage r. 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 guess that systemd-logind sends the "sleep" signal to network-manager, but network-manager never sends back the "wake" signal. So, the solution would be to just stop sending the "sleep" signal to network-manager on suspend.
PS: Am I talking to myself ? :)