Bug 204345 - After update to KDE 4.3.0 suspend/hibernate not working from menu
Summary: After update to KDE 4.3.0 suspend/hibernate not working from menu
Status: RESOLVED NOT A BUG
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-19 00:03 UTC by Sebastian Vahl
Modified: 2010-10-02 12:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Vahl 2009-08-19 00:03:09 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Fedora RPMs

After updating to KDE 4.3.0 I see some curious behaviour when trying to suspend/hibernate from the menu:

With my normal user account (and quite old config files) suspend/hibernate isn't working from inside the menu. After clicking on the buttons nothing happens. There are also no entries in the relevant logs (/var/log/messages,
/var/log/secure, /var/log/pm-suspend, ~/.xsession-errors). "solid-powermanagement suspend to_ram" instead is working.
After trying around with a clean user account I've found out that there are two ways to make suspend working again:

1. Enable PowerDevil
I've disabled PowerDevil because the description in systemsettings described it as a daemon for laptops. After enabling it again suspend/hibernate from menu is working again.

2. remove a custom file in ~/.kde/env
There I have a workaround script for my dual head layout which contains only one line (xrandr.sh):
xrandr --output DVI-0 --mode 1152x864 --left-of VGA-0

After I remove this script suspend/hibernate is working, although PowerDevil itself isn't running.

I could also reproduce this with a clean user account where I've only copied over ~/.kde/share/config and ~/.kde/env. I've also tried to remove some config files via trial&error to get the one that's also triggering the suspend. But until now I wasn't successfull.


So ATM I could summarize my issues like this (+ means working, - means not working suspend):
+ "solid-powermanagement suspend to_ram" is working all the time. 
+ With PowerDevil enabled suspend is working all the time. 
+ With PowerDevil disabled and some config files from my old .kde/share/config
and without .kde/env/xrandr.sh being present suspend is working
- With PowerDevil disabled and some config files from my old .kde/share/config
and with .kde/env/xrandr.sh being present suspend isn't working
- With PowerDevil disabled on a clean user account suspend isn't working


So this bug may contain two seperate issues:

1. If PowerDevil is disabled the menu items are doing nothing. This should not happen. At least an information dialog should be shown that PowerDevil is needed to do this. Additionally the description in systemsettings should be re-worked so that it doesn't assume to be only needed for laptops.

2. Some old config files from my user account seems to also trigger the suspend, although PowerDevil itself isn't running. I don't know which file and could need some help for debugging this.


Additional notes:
- If "powerdevil-daemon" isn't the right place for this bug, please re-assign it. I wasn't sure where to file it and because PowerDevil is at least partly involved I've choosed this component.
- I know that this bug is maybe describing seperate issues. But I have to write it down in one bug so that you could get the context. I'll file seperate bugs if you tell me so, of course.
- At least the issue with my old config files are hard to reproduce on a clean user account. If you ask me I could try to upload a tarball of them so that you could try it on your own (I have to remove some personal information first).
Comment 1 Dario Freddi 2009-12-01 18:46:42 UTC
Thanks for the report and sorry for the delay.

I'm marking the bug as invalid, read further.

Yes, powerdevil is required for suspension. Though you could file a bug against kickoff to let it use solid if powerdevil is not active, which would make somehow sense.

About the config files, you can send them to my mail ( drf at kde dot org ) to preserve your privacy, then I'll tell you to open another bug if needed (or just reopen this one)