Bug 233007 - power button set to suspend disk but nothing happens
Summary: power button set to suspend disk but nothing happens
Status: RESOLVED DOWNSTREAM
Alias: None
Product: solid
Classification: Unclassified
Component: powermanagement-daemon (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-01 22:40 UTC by Tom Chiverton
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 Tom Chiverton 2010-04-01 22:40:44 UTC
Version:           1.0 (using 4.4.2 (KDE 4.4.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.32-18-generic

Even though in 'power management' I have 'when power button pressed' set to 'suspend to disk' set in all profiles (and can confirm which is selected via the system tray icon), nothing happens when I press the power button.

This worked in KDE 4.x under 9.10, appears broken by using the 10.4 beta.

Hardware is a Dell Inspiron 1525 laptop.
Comment 1 Tom Chiverton 2010-04-09 23:26:45 UTC
Worse under Ubuntu 10.4 beta 2's packages, now the screen changes to a Kubuntu logo with animated dots underneath and hangs there.

CTRL-ALT-F1 swaps to text console but the keyboard doesn't respond when I try to login.

I *suspect* it's trying to reboot, and the hang is due to my CIFS mounts not being pulled down before the wireless is, but that's a different bug; it should be hibernating, not rebooting.

Using the 'suspend to disk' option on the logout dialogue all is well.

This was rock solid under 9.10 with Kubuntu backports of the same KDE4 version...
Comment 2 Tom Chiverton 2010-04-30 19:48:59 UTC
Using buttons added to the main menu panel work fine too.
Comment 3 Tom Chiverton 2010-05-03 23:40:47 UTC
As per https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/553557/comments/9 and following exploration, this appears to be something in Kubuntu or Ubuntu's packaging that causes the ACPI scripts to thing KDE isn't running, and do their default thing (power down).