Bug 268396

Summary: Clicking "Apply" in Power Management Global Settings doesn't work properly
Product: [Frameworks and Libraries] solid Reporter: Gabe A <gabextreme>
Component: powermanagement-kcmAssignee: Dario Freddi <drf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: jnelson-kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: This is the dialog in question. I'd just clicked "Apply" before taking this screenshot.

Description Gabe A 2011-03-13 18:43:04 UTC 
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

Selecting “Apply” in Power Management's Global Settings does not work. After pressing, the profile assignments flicker briefly, but the Apply button does not gray out and the changes do not take. When attempting to navigate away from the page, the Apply Settings dialog appears and prompts if the user wants to save changes.

Reproducible: Didn't try

Steps to Reproduce:
1. Open Power Management General Settings Dialog. 
2. Change a Profile Setting
3. Click Apply.
4. Observe that the button does not gray out.
5. Attempt to navigate away from the page, click a different tab, close the window, etc.
6. Observe that the "save changes" dialog appears.

Actual Results:  
Apply does not work. Button is not grayed out after clicking, settings do not take, and navigating away prompts the save changes dialog. 

Expected Results:  
Apply should function, the button should be grayed, the changes should take effect immediately, and navigating away should not produce the 'apply changes' dialog.

Default settings.
Comment 1 Gabe A 2011-03-14 19:33:30 UTC 
Created attachment 57993 [details]
This is the dialog in question. I'd just clicked "Apply" before taking this screenshot.
Comment 2 Gabe A 2011-03-15 17:45:47 UTC 
I meant "Reproducible: Always"
Comment 3 Dario Freddi 2011-09-30 09:47:19 UTC 
*** Bug 271305 has been marked as a duplicate of this bug. ***
Comment 4 Dario Freddi 2011-09-30 10:57:42 UTC 

*** This bug has been marked as a duplicate of bug 263658 ***