Bug 428371 - change theme frome breeze to breezeDrak not correctly done.
Summary: change theme frome breeze to breezeDrak not correctly done.
Status: RESOLVED DUPLICATE of bug 427864
Alias: None
Product: Breeze
Classification: Plasma
Component: general (show other bugs)
Version: 5.20.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-28 02:53 UTC by spphinslove
Modified: 2020-10-29 19:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
white block in dark theme (143.13 KB, image/png)
2020-10-28 02:53 UTC, spphinslove
Details
tray title bar (108.76 KB, image/png)
2020-10-28 02:55 UTC, spphinslove
Details
GTK application still white theme (37.76 KB, image/png)
2020-10-28 02:55 UTC, spphinslove
Details

Note You need to log in before you can comment on or make changes to this bug.
Description spphinslove 2020-10-28 02:53:10 UTC
Created attachment 132817 [details]
white block in dark theme

There is some white block in systemsetting5 also the tray title bar.
and gtk application not change theme colors unless you reboot.
if you change colors scheme,can make white block disappear and GTK application change to dark theme.

STEPS TO REPRODUCE
1. change theme to BreezeDark or just exec lookandfeeltool -a org.kde.breezedark.desktop
2. 
3. 

OBSERVED RESULT
change to dark theme

EXPECTED RESULT
some white blocks and not work for gtk applications.

Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.1-zen2-1-zen
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: GeForce GTX 1650/PCIe/SSE2

ADDITIONAL INFORMATION
Comment 1 spphinslove 2020-10-28 02:55:07 UTC
Created attachment 132818 [details]
tray title bar
Comment 2 spphinslove 2020-10-28 02:55:51 UTC
Created attachment 132819 [details]
GTK application still white theme
Comment 3 Nate Graham 2020-10-29 19:15:26 UTC

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