Reply to topic

Suspend-to-RAM doesn't work after upgrading to KDE 4.11

xapienz
Registered Member
Posts
14
Karma
0
OS
I don't think I should post it as bug, because it seems I miss something.

When I run select "Suspend" or run in konsole the following command, I only get my screen locked by screensaver. And the computer doesn't suspend.
Code: Select all
qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/SuspendSession suspendToRam



However, these commands:
Code: Select all
pm-suspend
and
Code: Select all
qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend true
work as expected. I.e. I can suspend from command line (or using hotkey if I make it run this command), but I cannot make computer suspend using KDE.

KDE 4.11.0 in Kubuntu 13.10.
I suppose there are Solid's logs somewhere, but I couldn't find them :(
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
What is the output of "upower -d", in particular the last section under the title "Daemon:"?


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS
I get the following:
Code: Select all
$ upower -d
...
Daemon:
  daemon-version:  0.9.21
  can-suspend:     yes
  can-hibernate:   no
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   yes
  lid-is-present:  yes
  is-docked:       yes
xapienz
Registered Member
Posts
14
Karma
0
OS
It seems one of the latest updates of kubuntu fixed this problem.
During installing updates, my computer suddenly went to suspend mode. I switched it on back. Then I saw message about "kded4" crash.
And after this going to suspend using kde works fine.
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
Okay. The output you posted definitely indicated that UPower believed your system was not capable of suspending - and that the lid was closed. It was likely this condition that caused KDE to immediately suspend your system when it became possible to (as a result of the updates).

Topic marked as solved.


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS

Fri Aug 23, 2013 8:45 am
No, finally it doesn't suspend again after system reboot. Seems that crash of kded4 did something for a short time, but the problem persists.

UPower believed your system was not capable of suspending

No, there was "can-suspend: yes". It showed it can suspend.

And yes, the lid was closed: I'm using dock-station and my notebook is closed.
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
Oops. I transposed the lines.
What is the output of this command?
Code: Select all
qdbus org.kde.kded /org/freedesktop/PowerManagement CanSuspend


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS

Fri Aug 23, 2013 10:34 am
Code: Select all
$ qdbus org.kde.kded /org/freedesktop/PowerManagement CanSuspend                                                       
true
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
Does the following command cause your system to suspend?
Code: Select all
qdbus org.kde.kded /org/freedesktop/PowerManagement Suspend


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS

Sat Aug 24, 2013 11:47 am
No, it doesn't. It only starts screensaver
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
Okay - that is the real cause of the issue. Your system is not entering suspend mode when KDE requests it to.
Do you see a process called "polkit-kde-authentication-agent-1" running on your system (or any other process with polkit in the name)?


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS
I have the following running processes with 'polkit' in name:

    /usr/lib/policykit-1/polkitd
    /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
What is output if you run the following command?
Code: Select all
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend


System Settings and Device Actions KCM maintainer
Image
xapienz
Registered Member
Posts
14
Karma
0
OS
Code: Select all
$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
Error org.freedesktop.UPower.GeneralError: Sleep has already been requested and is pending
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
This means you have an application which is inhibiting sleep - something which UPower and KDE are both respecting.
Download managers, disc burning applications, etc are likely to inhibit sleep.


System Settings and Device Actions KCM maintainer
Image

 
Reply to topic

Bookmarks



Who is online

Registered users: 16777216, alake, Baidu [Spider], Bing [Bot], edmael, Exabot [Bot], garthecho, Google [Bot], Hans, joshaughnessy, koriun, Majestic-12 [Bot], north, raymondsarver, urgo, verbalshadow, Yahoo [Bot]