Ubuntu
systemd-shim package

Suspend takes >20 seconds

Bug #1253456 reported by Philipp Keck
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd-shim (Ubuntu)
New
Undecided
Unassigned

Bug Description

My ThinkPad X220 with Ubuntu 13.10 (upgraded from previous versions) takes 20 seconds or more to suspend. This wasn't the case with 13.04.

During those 20 seconds I can reactivate the screen (which turns off properly) and then login and use the laptop (until it suspends after some time). If I login before suspend, I don't have to login on resume.

The issue is present with all of these ways to suspend:
- closing the lid
- using the Unity menu -> "Suspend"
- sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m

Calling "sudo pm-suspend" on the other hand always works immediately. I can't use this as a workaround, because it doesn't ask for the password on resume.

For logs, see this bugreport: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121)
pm-utils version is 1.4.1-12ubuntu1

I don't know if this is designed like this on purpose or a (related?) bug: The login screen I get after resume is quite different from the one I get on normal startup (see other bug report for details on that).

Revision history for this message
Martin Pitt (pitti) wrote :

> I don't know if this is designed like this on purpose or a (related?) bug: The login screen I get after resume is quite different from the one I get on normal startup

Yes, that's the screensaver, while the initial one is lightdm.

As pm-suspend works, this is not a bug in pm-utils but somewhere in the higher levels. Can you please enable system D-BUS debugging as on https://wiki.ubuntu.com/DebuggingDBus and create/attach a system D-BUS debug log what happens when you run "sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 [...]" or just use the unity menu?

affects: pm-utils (Ubuntu) → systemd-shim (Ubuntu)
Changed in systemd-shim (Ubuntu):
status: New → Incomplete
Revision history for this message
Philipp Keck (philipp-v) wrote :

Thank you for your answer. I will try to do that, however I don't know much about D-BUS. I managed to activate the system bus logging and dbus-monitor outputs a lot now. However that's too much for my console window and it is without timestamps. How can I get a useful logfile that I can upload here?

Revision history for this message
Philipp Keck (philipp-v) wrote :

I attached a logfile (without timestamps, because I don't know how) that was recorded during "sudo gdbus call -y -d [...]", 30 seconds of waiting, resuming the computer from standby and entering the password.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd-shim (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd-shim (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Philipp Keck (philipp-v) wrote :

This bug still occurs on my device,

Changed in systemd-shim (Ubuntu):
status: Expired → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.