Bug 455537 - Header colour doesn't properly update when using wallpaper accent and changing the wallpaper
Summary: Header colour doesn't properly update when using wallpaper accent and changin...
Status: RESOLVED DUPLICATE of bug 454047
Alias: None
Product: Breeze
Classification: Plasma
Component: QStyle (show other bugs)
Version: 5.25.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-18 09:54 UTC by Reiddragon
Modified: 2022-07-05 18:07 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
vid showing the bug in action, (excuse the blurriness, sub 100% scaling be doing that)) (564.90 KB, video/webm)
2022-06-18 09:54 UTC, Reiddragon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Reiddragon 2022-06-18 09:54:57 UTC
Created attachment 149884 [details]
vid showing the bug in action, (excuse the blurriness, sub 100% scaling be doing that))

SUMMARY
When using "Tint all colours with accent colour" and picking the accent colour from the current wallpaper, the header lags behind a colourscheme as the wallpaper updates
e.g. current wall is red, you set the scheme, all's good, you update the wall to blue, the header is still red, update the wall to pink, the header only now turns blue

STEPS TO REPRODUCE
1. Enable "Tint all colours with accent colour" for a colourscheme and apply it
2. Use accent colour from current wallpaper
3. change the wallpaper cycling between a couple with very different dominant colours

OBSERVED RESULT
the header is always 1 colour behind

EXPECTED RESULT
header should update together with everything else

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.59
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Comment 1 The Feren OS Dev 2022-06-18 10:45:52 UTC

*** This bug has been marked as a duplicate of bug 455142 ***
Comment 2 Nate Graham 2022-07-05 18:07:47 UTC

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