dx-packages team mailing list archive

[Pablo180 <1252121@xxxxxxxxxxxxxxxxxx>]

@Seth Arnold, Justin may have the package Linux installed but clearly he
is lacking its dependencies:

sarcasm-1.2.1
pretentiousness-99.9
elitism-1.0.1
smugness-1.0.0

Seth you seem to have an extra package installed:

unhelpfulness-0.1.1

Justin, you won’t need to restart every time, you can just enter:

sudo nmcli nm sleep false

or

sudo killall NetworkManager

This is an annoying bug, that you wouldn’t expect to see in Ubuntu these
days (I didn't see anything like this from the start) and I would
describe it as serious, I mean how many people like Justin would have no
idea how to get their networking back? I am guessing most new Ubuntu
users, as it is not like they can search the net for a solution is it?

Yanpas, thanks will try 2) as that has to be easier than having to open
a terminal each and every time I resume. It also makes me wonder about
those that don't have this bug, is it merely because many people  have
that enabled?

-- 
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 NetworkManager:
  New
Status in wicd:
  New
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/network-manager/+bug/1252121/+subscriptions