Version: 4.7 (using Devel) OS: Linux Actually their configuration window is displayed with default values selected. Example: - amarok here is configured to not display osd and use system notification. Untill configuration window wasn't open application respects my settings. But if I go to "settings->configure Amarok/Notification" following options are enabled: - use on-screen display (OSD) - use custom colors - custom color: red instead of everything but "use system notifications" set to off. I observed similar behaviour in some other apps including Kopete and BlueDevil KCM. Purging config files won't solve the issue (removed all config dirs (~/.kde, ~/.config, ~/.local of my test user before login). Because it happens with few independent apps I believe it's kdelibs problem Reproducible: Always Steps to Reproduce: 1. Start any of the affected apps 2. Go to settings->configure and set some options (like systray icons visibility etc..) and apply settings. 3. Open configuration window once again Actual Results: Configuration window shows different settings that were selected. If user applies settings, application uses new (wrong) settings Expected Results: Configuration window shows correct settings applied by the user.
I experienced this testing 4.6.90, but not with 4.6.95. What version(s) have you tried?
As in topic: KDE 4.7 RC1/2 that means 4.6.90 and 4.6.95 ;)
Nevermind, testing fail. I rechecked with several apps, amarok, kopete (kdenetwork-4.6.95), and these are not saving their settings properly. confirmed. Other apps did work ok, including k3b, konsole, konqueror. Strange.
Cannot reproduce on today's master. I only tested the "Configure Amarok/Notification" page, and settings there, including custom color, delay etc. are saved correctly across invokations.
Using 4.6.95 ~/.xsession-errors is showing many lines similar to the following when opening the configuration dialog: kopete(2143)/kdeui (KConfigDialogManager) KConfigDialogManager::setProperty: QCheckBox widget not handled! I am guessing it's related.
Is this using Qt 4.8?
I don't know about the others but i am (qt-4.8.0-0.1.tp.fc15.x86_64 from kde-redhat). I forgot all about that update. I will try downgrading to whatever the latest 4.7 is tomorrow and see if that fixes things.
I tested using qt-4.7.3
Jeremy pushed a possible fix to 4.7 branch today. If it is still happening on 4.7.0, please add a comment.
*** Bug 278300 has been marked as a duplicate of this bug. ***
Issue seems to be resolved in KDE 4.7.0 final