Bug 396082 - [New QML KCMs] KCM modules do not save settings properly
Summary: [New QML KCMs] KCM modules do not save settings properly
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.14.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 396293 396654 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-07-02 10:13 UTC by elman
Modified: 2019-01-14 23:17 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
KCM (109.89 KB, image/png)
2018-07-02 10:13 UTC, elman
Details
KCM2 (114.19 KB, image/png)
2018-07-02 10:14 UTC, elman
Details
KCM3 (114.06 KB, image/png)
2018-07-02 10:14 UTC, elman
Details
KCM4 (72.16 KB, image/png)
2018-07-02 10:15 UTC, elman
Details
KCM icons (70.65 KB, image/png)
2018-07-02 10:45 UTC, elman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description elman 2018-07-02 10:13:51 UTC
Created attachment 113704 [details]
KCM

After upgrade to Plasma 5.13.2, KCM panels do not save settings and show incorrect information.

For example Fonts.
1. Open System Settings
2. Click Fonts - everything seems fine
3. Click Icons
4. Click Fonts
5. Sub-pixel rendering and Hinting are now set to "Vendor Default"
6. Click Colors
7. Click Fonts
8. Adjust All fonts are now shown as "\1djust All Fonts..."

I'm experiencing similar weird behaviour also with Touchpad settings and Mouse Cursors.
Comment 1 elman 2018-07-02 10:14:24 UTC
Created attachment 113705 [details]
KCM2
Comment 2 elman 2018-07-02 10:14:47 UTC
Created attachment 113706 [details]
KCM3
Comment 3 elman 2018-07-02 10:15:04 UTC
Created attachment 113707 [details]
KCM4
Comment 4 elman 2018-07-02 10:45:23 UTC
I also have different issue which might be related:

- Window decorations do not use cursor theme selected via KCM. They seem to use Adwaita cursor theme, which is first in the list
- Flatpak apps use different desktop theme. I have Breath and flatpak apps use Breeze
- KCM frequently used icons are not shown. See attachment.
Comment 5 elman 2018-07-02 10:45:53 UTC
Created attachment 113711 [details]
KCM icons
Comment 6 Nate Graham 2018-07-13 20:35:33 UTC
All of these KCMs are the recently re-done ones...
Comment 7 Nate Graham 2018-07-13 20:39:12 UTC
*** Bug 396293 has been marked as a duplicate of this bug. ***
Comment 8 elman 2018-07-13 23:36:30 UTC
I recently noticed about Touchpad settings that when I do fresh boot, touchpad settings seem to be correctly applied. When I enable bluetooth mouse (which disables touchpad) and then I re-enable touchpad, settings are not applied correctly and I see warning as in KCM4 screenshot.
Comment 9 Christoph Feck 2018-08-02 20:59:24 UTC
*** Bug 396654 has been marked as a duplicate of this bug. ***
Comment 10 apache 2018-08-26 09:04:54 UTC
This maybe related. Plasma has general problem with saving settings.

https://bugs.kde.org/show_bug.cgi?id=390890

https://bugs.kde.org/show_bug.cgi?id=356899#c21

I also can't save qtcurve settings in Plasma system setting. Plasma always gets back to previous state.
Comment 11 Nate Graham 2019-01-12 22:51:14 UTC
Is anyone able to reproduce this? I can't in 5.14.5 or git master.
Comment 12 Matej Mrenica 2019-01-13 08:08:47 UTC
(In reply to Nate Graham from comment #11)
> Is anyone able to reproduce this? I can't in 5.14.5 or git master.

Window decorations kcm still shows prompt to save settings even when nothing was changed. Is it this bug?
Comment 13 Patrick Silva 2019-01-13 09:08:40 UTC
(In reply to mthw0 from comment #12)
> Window decorations kcm still shows prompt to save settings even when nothing
> was changed. Is it this bug?
it's already fixed. See bug 381806.
Comment 14 Matej Mrenica 2019-01-13 11:52:35 UTC
(In reply to Patrick Silva from comment #13)
> (In reply to mthw0 from comment #12)
> > Window decorations kcm still shows prompt to save settings even when nothing
> > was changed. Is it this bug?
> it's already fixed. See bug 381806.

Then no, I don't have this bug.
Comment 15 Nate Graham 2019-01-13 14:58:49 UTC
That was always a different bug anyway. :)
Comment 16 nuc 2019-01-13 15:19:24 UTC
I also cannot reproduce this anymore
Comment 17 elman 2019-01-14 23:17:19 UTC
I also can't reproduce this error anymore. Thanks guys.