Bugzilla – Bug 221715
Functionality for configuring lid close event etc. to trigger suspend not in YaST any more, but kpowersave doesn't have them either
Last modified: 2007-02-20 20:00:18 UTC
The options for configuring what should happen when a laptop user closes the lid, presses the suspend button etc. where removed from YaST, but kpowersave doesn't have a replacement for them. I was told that gnome-power-manager has those options. For laptop users this is a very visible regression from 10.1. :-(
Yes, something very unfortunate. Reassigning...
There was no FATE request to do this via KPowersave GUI (or to move features from Yast to KPowersave). Move this to 10.3 and please add a FATE request.
(In reply to comment #2) > There was no FATE request to do this via KPowersave GUI Are you joking? How are KDE users expected to change these settings? I understand that you don't have the time to add this to KPowersave for 10.2 and see the following possibilities: a) revert the changes to the YaST module so that it can be configured there or b) at least add something[tm] to the release notes Needless to say that this is not an enhancement, but a a real bug. (You could argue that it's an enhancement for KPowersave, but it's a bug in YaST and/or the whole picture ;-)
No, I'm not joking and yes this is an enhancement for KPowersave atm. And there is no way to add this to YaST. And please don't change the product for the bug
(In reply to comment #5) > No, I'm not joking and yes this is an enhancement for KPowersave atm. > And there is no way to add this to YaST. Bad, but understandable in RC1 state ;-) > And please don't change the product for the bug OK, I won't touch it. My question remains: How are KDE users expected to change these settings? (-> Release Notes?)
Here is a small tutorial: http://dkukawka.blogspot.com/2006/11/kpowersave-config-tutorial.html I add later the same at opensuse. Maybe add a link to the site at opensuse (I would use: http://en.opensuse.org/KPowersave_0.7.x_config_tutorial) to releasenotes and add something like this: "The user can't configure some of the new KPowersave features via the config dialog, but via the config file. Please read this instructions: http://en.opensuse.org/KPowersave_0.7.x_config_tutorial until a update is released."
*** Bug 216317 has been marked as a duplicate of this bug. ***
Karl, please get the comment from #8 in the release notes (perhaps via a separate bug).
Would be handy to have the equivalent notes for gnome-power-manager users too.
(In reply to comment #11) > Would be handy to have the equivalent notes for gnome-power-manager users too. I don't know how this work at g-p-m and if this all is possible there. Maybe Rodrigo can say more about this.
If you know that you do it through g-p-m, it's easy and GUI-driven (right-click on g-p-m, select Preferences, change the actions for when on AC and when on Battery. Perhaps just a note in the release notes to this effect?
But why a note for g-p-m if this can be done via GUI. This should be obvious.
We definitely should rephrase the above release note sentence. As it is written now, it sounds like it is by design, which isn't.
(In reply to comment #14) > But why a note for g-p-m if this can be done via GUI. This should be obvious. Should be :) For people (like me) who have been used to doing it via YaST in the past, it's worth giving the note that controlling this functionality has moved.
(In reply to comment #15) > We definitely should rephrase the above release note sentence. As it is > written now, it sounds like it is by design, which isn't. The please make a proposal for an other text if you mean the text from comment #8 (but I would say "until a update is released" say clearly that the current state is not by design).
Once decided, please assign the bug to me for adding it to the RNs.
*** Bug 223922 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > Here is a small tutorial: > http://dkukawka.blogspot.com/2006/11/kpowersave-config-tutorial.html > > I add later the same at opensuse. > > Maybe add a link to the site at opensuse (I would use: > http://en.opensuse.org/KPowersave_0.7.x_config_tutorial) to releasenotes and > add something like this: > > "The user can't configure some of the new KPowersave features via the config > dialog, but via the config file. Please read this instructions: > http://en.opensuse.org/KPowersave_0.7.x_config_tutorial until a update is > released." > There is NO way to configure Power Button Events. :( So I would consider this as a real Bug in 10.2 for KDE Users. The only way to make the power button work is not to use kpowersave. At least add some kpowersaverc or eventsrc support for Power Button Events as some *basic* acpi feature is missing in 10.2/KDE. This is just some more food for (K)ubuntu trolls ("wah? no acpi button handling in susi?? *ololol* use Kubuntu!!!!11")
*** Bug 228199 has been marked as a duplicate of this bug. ***
*** Bug 230841 has been marked as a duplicate of this bug. ***
*** Bug 230750 has been marked as a duplicate of this bug. ***
Robin, you have to use sysconfig editor -- nasty, but it works. Of course as long as you DO NOT use kpowersave.
I don't want to make mess, but: a) if it is some kind of summary report -- retitling would be a good idea b) it is really a bug report, for KDE users pretty serious, not a wish
*** Bug 229315 has been marked as a duplicate of this bug. ***
*** Bug 230688 has been marked as a duplicate of this bug. ***
*** Bug 229045 has been marked as a duplicate of this bug. ***
*** Bug 231805 has been marked as a duplicate of this bug. ***
*** Bug 232472 has been marked as a duplicate of this bug. ***
*** Bug 232075 has been marked as a duplicate of this bug. ***
This is the number one issue reported with 10.2 wrt. power management IMO, so "enhancement" does not really fit well.
(In reply to comment #25) > Robin, you have to use sysconfig editor -- nasty, but it works. Of course as > long as you DO NOT use kpowersave. > No, not really. The sysconfig editor configures powersaved events. But if kpowersave is running, powersaved ignores these events. If I kill kpowersave, they work fine.
(In reply to comment #35) > (In reply to comment #25) > > Robin, you have to use sysconfig editor -- nasty, but it works. Of course as > > long as you DO NOT use kpowersave. > > > > No, not really. > The sysconfig editor configures powersaved events. > But if kpowersave is running, powersaved ignores these events. > > If I kill kpowersave, they work fine. > Oh.. you already said that ;) (overlooked your second sentence)
submitted package for YOU update
Great! But... what's the fix? Or where do we go to edit this after the update is applied? Thanks.