Debian Bug report logs - #729659
general: problem with laptop suspend after dist-upgrade

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Kuba <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: general: problem with laptop suspend after dist-upgrade

Date: Fri, 15 Nov 2013 12:47:16 +0100

Package: general
Severity: normal

Dear Maintainer,
After running apt-get dist-upgrade, my laptop does not suspend properly:
Problems:
1) key shortcut - used to work (standard shortcut, worked out of the box), now
instead suspending, it causes screen lock
2) menu option - used to be above power off option (in gnome menu, this in top
right), now disapeared
3) closing lid - does nothing, used to suspend

when I type some magical command (found on http://askubuntu.com/questions/1792
/how-can-i-suspend-hibernate-from-command-line):
dbus-send --system --print-reply \
    --dest="org.freedesktop.UPower" \
    /org/freedesktop/UPower \
    org.freedesktop.UPower.Suspend
system suspends propperly

laptop: Lenovo thinkpad t61p

Chears,
Kuba



-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Message #12 received at [email protected] (full text, mbox, reply):

From: Holger Levsen <[email protected]>

To: [email protected]

Cc: [email protected]

Subject: Re: Processed: Re: Bug#729659: general: problem with laptop suspend after dist-upgrade

Date: Fri, 15 Nov 2013 19:12:21 +0100

[Message part 1 (text/plain, inline)]

reassign 729659 upower
# if it affects upower those maintainer know better than the '"general" 
# maintainers' what to do with this bug...
thanks

[signature.asc (application/pgp-signature, inline)]

Message #19 received at [email protected] (full text, mbox, reply):

From: Eric Valette <[email protected]>

To: [email protected]

Subject: same here on all machines after upgrade

Date: Sun, 01 Jun 2014 19:51:35 +0200

I have exactly the same problem and it starts annoying me quite a lot 
because it's happening on all my machines:

qdbus org.kde.kded /org/freedesktop/PowerManagement CanSuspend
false

dbus-send --system --print-reply --dest="org.freedesktop.UPower" 
/org/freedesktop/UPower org.freedesktop.UPower.Suspend
Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with 
signature "" on interface "org.freedesktop.UPower" doesn't exist


of course calling pm-suspend directly works as expected!


-- eric

Message #24 received at [email protected] (full text, mbox, reply):

From: Francois Gouget <[email protected]>

To: [email protected]

Subject: Re: general: problem with laptop suspend after dist-upgrade

Date: Wed, 27 Aug 2014 11:08:04 +0200 (CEST)

Eric Valette is being bugged by this issue:
> dbus-send --system --print-reply --dest="org.freedesktop.UPower" 
> /org/freedesktop/UPower org.freedesktop.UPower.Suspend
> Error org.freedesktop.DBus.Error.UnknownMethod: Method "Suspend" with 
> signature "" on interface "org.freedesktop.UPower" doesn't exist

I ran into this too and as far as I can tell this happens because UPower 
has been superseded by Systemd.Logind. So the fix I found is to make the 
following call instead:

dbus-send --print-reply --system --dest=org.freedesktop.login1 \
    /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend \
    boolean:true

There are similar commands for HybridSleep and Hibernate. The 
Systemd.Logind documentation can be found there:

http://www.freedesktop.org/wiki/Software/systemd/logind/

-- 
Francois Gouget <[email protected]>              http://fgouget.free.fr/
             Research is the transformation of money to knowledge.
            Innovation is the transformation of knowledge to money.
                              -- Dr. Hans Meixner

Send a report that this bug log contains spam.