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.