Bug 493678 - Color settings not taking effect without select another theme in between
Summary: Color settings not taking effect without select another theme in between
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_colors (show other bugs)
Version: 6.1.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-26 07:47 UTC by Lassi Väätämöinen
Modified: 2024-09-26 18:53 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lassi Väätämöinen 2024-09-26 07:47:32 UTC
SUMMARY
Color settings not taking effect upon "Apply", but need to change to another scheme and then back to the one you edited 


STEPS TO REPRODUCE
1. System settings -> Colors and Themes -> Colors
2. "openSUSE Dark" -> Edit color scheme -> Save As -> "openSUSE Dark mine"
3. Edit the new color theme: Inactive titlebar: pick a color and save.
4. Apply
5. Select another theme -> Apply
6. re-select the "openSUSE dark mine"
7 Apply

OBSERVED RESULT
Inactive titlebar color does not change to what was selected  upon first Apply, at step #4.

EXPECTED RESULT
Titlebar color should change after Apply in step #4, without the need to switch to another color scheme.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed-Slowroll 20240803
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i7-11850H @ 2.50GHz
Memory: 46,8 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: LENOVO
Product Name: 20YRS21300
System Version: ThinkPad P15 Gen 2i

ADDITIONAL INFORMATION
openSUSE Dark works for testing, for example. Breeze Dark does not, there's another bug,  bug 493677.
Comment 1 Nate Graham 2024-09-26 18:53:19 UTC
I see something slightly different on git master, likely due to recent color scheme editor changes that actually fixed this issue but introduced or exposed a separate one. So this bug is fixed, and I'll open a new one for the issue I see: Bug 493706