For me Martin's package solves the problem ~96.6% of the time, which is already great progress since before I was having the problem almost every time. I've tried suspending my machine about 30 times (10 times by closing the lid, 10 times by clicking the suspend button in the menu, and 10 times with pm-suspend), and I got only one case when the network didn't come back. In the failing case the error reported by systemd-logind was slightly different than before (see #34 for the previous error message): Lid closed. Suspending... Failed to send delayed message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Lid opened.
I no longer encountered the case when resumption didn't work at all (machine going back to sleep as in #34). And it happened twice that pm- suspend wouldn't do anything (with output from systemd-logind). Anyway, this is a step in the right direction, I would say :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
