dx-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Thanks LoÏc. For the record, it's expected that systemd-shim times out
after some seconds of inactivity. So the shim log looks fine, and indeed
the PrepareForSleep False is missing, as with other people. At this
point this requires an in-depth debugging of systemd-logind, to see  why
it sometimes fails to send out the PrepareForSleep false after resuming.
Supposedly systemd-shim doesn't simulate the suspend.target & friends
convincingly enough and we are missing something important there.

I'm not familiar with the inner workings of logind either, so I'm afraid
I cannot give much helpful advice what could be wrong there. Just some
hints if anyone wants to take a stab:

 - It's perfectly acceptable to kill a running logind and start it in
the foreground, even from a built tree; it will pick up the state from
/run/ and /sys/fs/cgroups/. That makes it easier for "add debug
info"/compile/run/suspend cycles.

 - It's probably also helpful to edit /usr/sbin/pm-suspend to "exit 0"
at the start, so that the machine doesn't actually suspend; of course
before doing this you should ensure that this actually still reproduces
the bug; if not, and it turns out to be some timing issue, then you
could also put a "sleep N" in front of it, and check for which values of
N it starts working/failing.

-- 
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:
  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/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions