This bug was fixed in the package systemd-shim - 6-0ubuntu0.13.10
---------------
systemd-shim (6-0ubuntu0.13.10) saucy-proposed; urgency=low
* New upstream bug fix release:
- Write a sendsigs.omit.d file to prevent upstart from killing us during
shutdown. That's the other half of preventing suspends during shutdown.
(LP: #1211514)
- Flush the right bus (system, not session), to address another case of
"PrepareForSleep signal is missing" which breaks networking after
resuming. (helps some people in LP: #1252121)
-- Martin Pitt <martin.p...@ubuntu.com> Tue, 10 Dec 2013 10:59:08 +0100
** Changed in: systemd-shim (Ubuntu Saucy)
Status: Fix Committed => Fix Released
--
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 “systemd-shim” package in Ubuntu:
Incomplete
Status in “systemd-shim” source package in Saucy:
Fix Released
Status in “systemd-shim” source package in Trusty:
Incomplete
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/ubuntu/+source/systemd-shim/+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
