Bug 306198 - does not remember values for disabled widgets
Summary: does not remember values for disabled widgets
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-kcm (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Dario Freddi
Depends on:
Blocks: extramile
  Show dependency treegraph
Reported: 2012-09-03 15:13 UTC by Aurelien Gateau
Modified: 2013-07-29 15:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Aurelien Gateau 2012-09-03 15:13:45 UTC
When one sets values in the kcm such as timeout and type of action in the "suspend session" group, then uncheck the "suspend session" option, timeout and type of action are not saved: next time kcm is restarted, they are back to their default value.

Reproducible: Always

Steps to Reproduce:
1. check "Suspend Session"
2. set a value for "After" and pick an action in the combo box
3. unckeck "Suspend Session"
4. close kcm
5. open kcm again
Actual Results:  
"Suspend Session / After" is back to its default value, combo box is empty.

Expected Results:  
"Suspend Session / After" and the combobox should remember the value which had been set.
Comment 1 Kai Uwe Broulik 2012-10-29 16:37:31 UTC
The cause of this is that PowerDevil removes the config when you uncheck the checkbox. And all profiles that are configured are automatically enabled, there is by design no way for a configured action to be disabled. Investigating/trying-to-fix right now
Comment 2 Alex Fiestas 2013-03-12 13:02:48 UTC
Any news on this Kai?
Comment 3 Kai Uwe Broulik 2013-03-12 13:04:09 UTC
It's on my 4.11 ToDo list :-)
Comment 4 Alex Fiestas 2013-07-28 21:57:18 UTC
Ping ?
Comment 5 Kai Uwe Broulik 2013-07-29 13:29:10 UTC
A bit more complicated than I thought at first …
Comment 6 Alex Fiestas 2013-07-29 15:29:58 UTC
We haven't been able to rework this for 4.11, and now it is frozen :/

Since this bug requires major changes that can't happen until KDE5, and we'll overhaul these part of the code by then I'm going to set this bug as WONT FIX.

Will make sure though this is polished in the new GUI :)