dx-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Daniel Hahler [2013-12-19 13:24 -0000]:
> With the normal suspend methd, PrepareForSleep=false showed up now (and
> the network came up again), (together with PrepareForSleep=true):

Interesting. To the other affected people: are you using hybrid
suspend or the "simple" (RAM only) suspend?

> Where is the PrepareForSleep=false signal emitted

That comes from logind, which is the component which provides the
"Suspend()" API for the desktop. It should send "PrepareForSleep
true", then it will wait until apps which registered a suspend
inhibitor are done with their pre-suspend actions, then do the actual
suspend, and after resume send the "PrepareForSleep=false" signal so
that clients can do their post-suspend actions.

> Is it something NetworkManager requires to wake up again?

Exactly. NM shuts down the network on PrepareForSleep=false, and
searches for networks/re-connects on PrepareForSleep=true.

-- 
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:
  Confirmed
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