Bug 271305 - Settings and Profile page doesn't handle 'Apply' properly
Summary: Settings and Profile page doesn't handle 'Apply' properly
Status: RESOLVED DUPLICATE of bug 268396
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-kcm (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
: 265038 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-19 17:59 UTC by Jon Nelson
Modified: 2011-09-30 09:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Nelson 2011-04-19 17:59:42 UTC 
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

When configuring the _Global_ power management settings, in the 'Settings and Profile' page, perform these steps.

1. note the 'Apply' button is greyed out

2. Check/Uncheck "Lock screen on resume".

3. Note 'Apply' button is now available.

4. Change it back. 

5. Note 'Apply' button is /still/ available (even though settings haven't changed from their original values.)

6. hit 'Apply' button.

7. NOTE: 'Apply' button does not change. No 'error' dialog.

8. HINT: check .xsession-errors and observe that every hit of the 'Apply' button is accompanied by this error message in .xsession-errors:

kded(2715) PowerDevilUPowerBackend::setBrightness: org.kde.powerdevil.backlighthelper.setbrightness failed 


Summary of issues:

1. failure to apply brightness settings prevents expected use of 'Apply' button
2. no error dialog was generated for failure to apply brightness settings



Reproducible: Always
Comment 1 Jon Nelson 2011-07-25 22:49:02 UTC 
As of 4.7RC2, the "hint" no longer applies, but the rest of the bug does.
Still an issue.
Comment 2 Jon Nelson 2011-07-29 16:41:41 UTC 
Still an issue as of 4.7.0 final.
:-(
Comment 3 Jon Nelson 2011-07-29 16:44:16 UTC 
*** Bug 265038 has been marked as a duplicate of this bug. ***
Comment 4 Dario Freddi 2011-09-30 09:47:19 UTC 

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