← Back to team overview

kernel-packages team mailing list archive

[Bug 1252121] Re: networkmanager networking is disabled on suspend-resume


Thanks Rafael, Gabriel, Philipp! Your logs agree in the fact that at the
time it tries to call, or called pm-suspend, the shim's D-BUS connection
goes away:

09:20:16 E: (process:3100): GLib-GIO-CRITICAL **:
g_dbus_connection_flush_sync: assertion 'G_IS_DBUS_CONNECTION
(connection)' failed

(and some noise around it). Rafael's log additionally shows

  15:05:35 E: ** (process:19670): WARNING **: Error while running

but not what kind of error unfortunately. At the moment I don't have an
idea what happens there, I'll discuss with Ryan and try to get something
like that by sprinkling some sleeps around pm-utils and the code.

Rafael and Gabriel's pm-suspend.log shows no oddities, and suspend looks
fairly fast. Philipp's pm-suspend log confirms that the suspend takes
some 30 seconds for him, which is absurdly long. That's yet another bug
(might be in pm-utils or in the kernel); Philipp, can you please report
it against pm-utils, and we debug it in another bug report?

So let's use this bug report for the broken D-BUS connection.

** Summary changed:

- networkmanager networking is disabled on suspend-resume
+ missing resume signal because D-BUS connection goes away

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  missing resume signal because D-BUS connection goes away

Status in “linux” package in Ubuntu:
Status in “systemd-shim” package in Ubuntu:

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)

To manage notifications about this bug go to: