[Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Seth Goldin]

The issue seems be resolved for me in Lubuntu 14.10.

On Wed Jan 21 2015 at 2:01:06 PM Andy Somerville <andy.somerville at gmail.com>
wrote:

> @r0lf this is still happening in 14.10/Utopic  should it be reopened
> there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   Won't Fix
> 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
>

-- 
You received this bug notification because you are a member of Network-
manager, which is subscribed to NetworkManager.
https://bugs.launchpad.net/bugs/1252121

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions