Philip, I also tried the Live CD version of 14.04 and discovered the same as you did that it did not suffer from this problem. However I remember some years ago trying the Live CD of a newly released version of Ubuntu and discovered that Suspend and Hibernate worked flawlessly, only to install the same version and discover that they didn’t work at all once Ubuntu was installed. So I don’t trust the Live version enough to attempt a complete re-install, probably only to discover that the problem is still present!
I have upgraded to 14.04 and as others have stated, the problem persists. It seems less frequent, but I think that part of that is that it seems to happen more when it has been suspended for a while, and I have only tested it by repeatedly closing and opening the lid today. Justin, I looked at your workaround but that folder is empty for me, so I cannot try it. Yanpas, I tried setting the password again on resume in 14.04, but with the same result as before, it didn’t work for me for Suspend. I’ve given up to be honest. This will probably be fixed upstream in a year or two. I’ve been using Ubuntu for ten years and can count on one hand the number of bugs I’ve seen fixed. Typically I find a workaround, forget all about and years later realise the problem has gone away. I am now using a workaround found here: http://ubuntuforums.org/showthread.php?t=1522146 This restarts NetworkManager on every resume. It is not ideal, but it works and is not dependent on anything else and won’t be overridden by an update. Problem solved. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
