Version: unspecified (using KDE 4.8.0) OS: Linux In previous KDE versions, (I do use F16 on my work laptop), i do use the power profiles option. Thanks to that incredible feature i am able to work much efciently. I do have one custom pofile created due to a special need: "DO NOT SUSPEND" I does all powersaving, even minimal brightness, exept that it does not suspen even when closing the lid. For an important reason: usb devices (serial ports, 3g modems) and a time: at work with critical procedures Since there are times in which i need to complete somewhat large non-interactive proceses in places with no ac power (and for example, go to lunch while on battery [charged, of cource :-)] I the profile is needed, for example, to be able to lunch, to the bathroom, etc while i am working with a usb serial port or 3g connection in a place without ac power. The current method has the somewhat cryptic "disable [ALL?] powersaving", whatever it means? (i do asume no suspend, governor perfomance, full panel brigtness, etc, aka no granularity). So, that custom profile was not default, because i don't do that all the time, i set it only when it makes sense, that was a plus. This new way seems to lead to enabling & disabling powersaving cycles, turning on/off some feature X before doing Y action all the time, it is a regression, if some actions requiere certain options, i set the options, put a name ad select the name when i think i will need these option instead of chaning all of them. I may live with 4.8.x way, but it needs further improvement. or maybe a quick-fix should be rename "disable powersaving" to "do not suspend" (asuming that previous option does only that). I know that nothing can be done for 4.8.x series, but please return some type of profiles, in my opinion ther where NEVER obsolete. Reproducible: Always Steps to Reproduce: it is not a bug but a design issue/feature request/ehancement Actual Results: it is not a bug but a design issue/feature request/ehancement Expected Results: it is not a bug but a design issue/feature request/ehancement it is not a bug but a design issue/feature request/ehancement
TL;DR: Your needs can be satisfied just by using the checkbox in the applet. As you might imagine we won't change a design choice we put lots of time into and which doesn't introduce any kind of regression (which is a completely different thing). You can have a look at http://drfav.wordpress.com/2011/10/02/forge-sprint-2011-power-management-and-its-future/ and http://drfav.wordpress.com/2011/10/04/power-management-a-new-screencast/ for understanding the new design better. The checkbox in the applet (which indeed could use a better wording) serves for disabling any idle-based action, in fact preventing the PC from suspending or dimming the screen when disabled. If you are still not satisfied and your use case is more complex (but I doubt it is), you can still resort to activity-based profiles.