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 '/usr/sbin/pm-suspend' 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing resume signal because D-BUS connection goes away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1252121/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
