Suspend-resume cycle pm-suspend.log
** Attachment added: pm-suspend.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3913273/+files/pm-suspend.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Suspend-resume cycle, network disabled on resume.
** Attachment added: systemd-shim.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3913271/+files/systemd-shim.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
In bug 1184262, Catalin made an interesting observation that this
failure seems to only happen for her when using the lid to suspend, but
not when using the session menu or power button.
It would be interesting if you ever get a suspend failure with this:
sudo gdbus call -y -d
Martin, adding the Exec line as requested results in failure of the
suspend portion of suspend-resume, so I cannot provide a log
--
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:
In the other bug report, I said that sudo pm-suspend didn't work,
which is wrong. Maybe I forgot to re-activate the network after some
previous test ...
So my current results are (tested 5 times):
All of these methods:
- closing the lid
- using the Unity menu - Suspend
- sudo gdbus call -y -d
pm-suspend.log after unsuccessful suspend-resume-cycle (i.e. network
didn't work afterwards).
** Attachment added: pm-suspend.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3912649/+files/pm-suspend.log
--
You received this bug notification because you
I just modified
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in the way
you asked. Then I suspended using the Unity menu. However, the laptop never
turned off (usually it does after 20-30s) - at least not for over a minute. So
I pressed I key and was able to login (and
Philipp, Gabriel: I'm sorry, I didn't consider that annotate-output
isn't installed by default. It's in the devscripts package. Please
install it with sudo apt-get install --no-install-recommends
devscripts. (It's useful to add timestamps to the log output).
--
You received this bug notification
I used the command in #6 and the system suspended normally. Upon resuming the
system the network was still diabled and I had to kill the networkmanger to
wake it up.
I attached the pm-suspend.log
** Attachment added: pm-suspend.log
** Attachment added: systemd-shim.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3912889/+files/systemd-shim.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Followed the instructions in #5.
** Attachment added: pm-suspend.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3912891/+files/pm-suspend.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey Martin, I tried the command you gave in comment #6, and I could
reproduce the network problem in 13 tries. Unfortunately this seems to
invalidate your hypothesis on only the lid closing causing the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Dbus log during suspend-resume as per
https://wiki.ubuntu.com/DebuggingDBus
** Attachment added: Dbus logging of suspend-resume
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+attachment/3911398/+files/suspend-dbus-log
--
You received this bug notification because you are a
Gabriel Devenyi, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal
Can you please modify (sudo gedit, for example) /usr/share/dbus-1
/system-services/org.freedesktop.systemd1.service to set the Exec= line
to
Exec=/bin/sh -c 'env G_DBUS_DEBUG=all annotate-output /usr/lib/x86_64
-linux-gnu/systemd-shim /tmp/systemd-shim.log 21'
Then please do a suspend/resume
The PrepareForSleep false signal is missing. Invalidating kernel task
to stop the kernel bug auto-responder from nagging (please ignore the
previous comment).
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of
17 matches
Mail list logo
