Bug 263658 - Push on Apply button in Global settings do nothing
Summary: Push on Apply button in Global settings do nothing
Status: RESOLVED FIXED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-kcm (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
: 268396 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-19 15:59 UTC by Žarko
Modified: 2011-09-30 10:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.6.1

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Žarko 2011-01-19 15:59:27 UTC 
Version:           unspecified (using KDE 4.5.95) 
OS:                Linux

If you change something in Powerdevil, in Global Settings and pess Apply button, nothing happened. Settings are saved only if you want to leave powerdevil and warn you about that.

Reproducible: Always

Steps to Reproduce:
Change something in Powerdevil's Global Settings and press Apply button to confirm.
Comment 1 Dario Freddi 2011-01-26 22:25:43 UTC 
SVN commit 1217364 by dafre:

BUG: 263658
FIXED-IN: 4.6.1

Forgot to emit changed(false), which caused saving to happen, but notification to the user to fail.

 M  +3 -0      GeneralPage.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1217364
Comment 2 Dario Freddi 2011-01-26 22:27:03 UTC 
SVN commit 1217365 by dafre:

Backporting r1217364

CCBUG: 263658

Forgot to emit changed(false), which caused saving to happen, but notification to the user to fail.


 M  +3 -0      GeneralPage.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1217365
Comment 3 Žarko 2011-03-06 21:54:24 UTC 
Sorry, but I'm now in KDE4.6.1 and this problem is not resolved!
Comment 4 Dario Freddi 2011-09-30 10:57:42 UTC 
*** Bug 268396 has been marked as a duplicate of this bug. ***
Comment 5 Dario Freddi 2011-09-30 10:58:41 UTC 
Closing this bug again - having a look around, apparently the fix was not delivered on 4.6.1 - although 4.7 should be more than fine.