Version: 4.3.3 (using KDE 4.3.3) Compiler: gcc-4.3.4 OS: Linux Installed from: Gentoo Packages This bug appears on my notebook, where I have configured the power manager to standby computer after 30 mins of inactivity when battery powered. To make it short, if the timeout is elapsed when the notebook is powered, next I remove the power plug before touching the keyboard/touchpad the action is performed even if the notebook didn't spend 30 minutes on battery power. Steps to reproduce: First settings, 1. In Power Management, Edit Profiles, set "Do Nothing" on the "When the system is idle for more than" combo box for the "Performance" profile. 2. In Power Management, Edit profiles, set "Suspend to RAM" on the "When the system is idle for more than" combo box for the "Powersave" profile and set 15 minutes. 3. In Power Management, General Settings, set "When AC Adaptor is plugged in" to profile "Performance" and "When on battery power" to the "Powersave" profile. Next, actions 4. With battery full and connected to power (therefore on the "Performance" profile) leave the computer idle for >15mins. 5. After say 20 mins unplug power cord. Results: The Standby to RAM action is initiated, leaving me 10 seconds to react. (Or 30 seconds, but still annoying) Expected results: The computer should perform the "standby" action after measuring 15mins of being idle _after_ unplugging the power chord.
Yes, it is extraordinarily annoying. I leave very often my laptop powered on and plugged in to let it chagre, and when I want to start working, I unplug it to make myself comfortable, and the computer suspends. I have seen this on F11 and F12, all versions of kde including the latest one.
I've been experiencing my laptop suspending to RAM when unplugging it on Debian squeeze probably since I had to upgrade to KDE 4. Yesterday, someone came on #debian and asked how he could report that bug, since he didn't know what package was guilty. After pointing him to the general pseudo-package, I realized he was describing a problem I also had. Since he had understood in which conditions it happened, I was able to track the issue to PowerDevil today. So this issue affects 2 more people. What this should show is that this bug probably affects a large number of people who find it difficult to track it down. Except for that, both of us use Debian squeeze with KDE, and were unaware we were using PowerDevil until yesterday. This will affect default squeeze installations with KDE if nothing is done.