Bug 436596 - Doesn't change color scheme live
Summary: Doesn't change color scheme live
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.27.8
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-04 17:04 UTC by Lua
Modified: 2025-09-18 22:27 UTC (History)
2 users (show)

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

Attachments
discover bug (860.84 KB, video/mp4)
2021-05-04 17:04 UTC, Lua 		Details
kirigami gallery (888.69 KB, video/mp4)
2021-05-07 21:20 UTC, Lua 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lua 2021-05-04 17:04:32 UTC 
Created attachment 138146 [details]
discover bug

SUMMARY
Also, if you change the color scheme again, Discover will follow the previous scheme you applied.

STEPS TO REPRODUCE
1. Open Discover;
2. Change the color scheme while Discover opened.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-05-04 18:52:56 UTC 
Cannot reproduce. Does it also happen with any other apps?
Comment 2 Lua 2021-05-04 21:28:06 UTC 
Just with Discover.
Comment 3 Aleix Pol 2021-05-06 12:52:14 UTC 
Can you compare it with another Kirigami app? Like the kirigami gallery for example.

FWIW I cannot reproduce either.
Comment 4 Lua 2021-05-07 21:20:05 UTC 
Created attachment 138229 [details]
kirigami gallery

This doesn't happen in Kirigami Gallery.
Comment 5 Lua 2021-06-06 21:44:37 UTC 
Same thing happens in KDE Connect.
Comment 6 Nate Graham 2023-10-17 17:03:55 UTC 
I'm able to reproduce this in Plasma 6 now.

Not a general Kirigami bug as most Kirigami apps do still change color live. Seems specific to Discover; moving there.
Comment 7 Nate Graham 2025-09-18 22:27:40 UTC 
I can't reproduce this issue anymore; it's since been fixed.