dx-packages team mailing list archive

[Philipp Keck <philipp@xxxxxxxxxxxxxx>]

Same here (13.10) . The big problem is that it seems to be in all releases, so downgrading from 13.10 to the previous LTS release wouldn't even help. Half a year ago, everything was fine. So why is it that now it suddenly does not work anymore and can't be fixed (e.g. by reverting some changes)?
For the last two months, I have used Ubuntu less and less often, instead I use Windows a lot more, because it saves me the 15-20 seconds that I need to workaround the issue after resuming Ubuntu.

Btw: Where do bug reports go that I send from within Ubuntu (with the
"Report a problem..." application, Apport)? I send tons of these because
right after boot I get two errors, sometimes more, and the software
updater regularly crashes, too. Maybe this is because my Ubuntu
installation is upgraded from 12.10 over 13.04 to 13.10? And may the
startup errors be related to this issue?

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