Since I upgraded all my devices to KDE 6 I have this weird issue with my laptop and media PC. The software update icon that sits in the tray and starts Discover seems to think I’m using a light plasma theme. It’s only this one icon, and it’s the same for all icon themes. I do not have this issue on my desktop, which has the same updates (comparison in screenshot).
I have tried the following to no avail:
- switching between multiple icon themes
- switching between KDE light and dark plasma themes
- deleting ~/.share/icon-cache.kcache
Anyone have any further ideas?
OS: Nobara release 39 (Thirty Nine) x86_64
Kernel: 6.7.6-201.fsync.fc39.x86_64
Shell: bash 5.2.26
Resolution: 2560x1440
DE: Plasma 6.0.1
WM: kwin
Theme: [Plasma], Breeze [GTK2/3]
Icons: Papirus [Plasma], Papirus [GTK2/3]
So I had some time to do some further testing into this issue and I made some “progress”.
On my desktop, who has the correctly displayed light icons for the dark plasma theme: if I straight up remove ~/.cache (rename it to ~/cache.bak) and reboot, several icons become black (update, gajim and steam). Meaning that somewhere in that cache (but not ~/.share/icon-cache.kcache, since I tried that already), the correct display of icons is located.
I’ll try to pinpoint it further and report back if I find anything.
I managed to track it down further. The issue is that some icons (Discover, Gajim, Steam) pull their light/dark info from the “Colours” instead of the “Plasma Style”. So If you mix and match like I did (Breeze Twilight, i.e. Breeze Dark Plasma Style with Light Colours), then most icons will appear light due to the Dark Plasma Style, but some will be dark because they get their Light/Dark info from the Light Colours.
That information seems to be cached in ~/.cache/plasmashell/qmlcache/. When I delete that folder I get the broken icons. I f I use the cached folder from my desktop it’s fixed. I’m guessing some apps just are broken currently in that regard and I’m just “lucky”, that my desktop didn’t correctly flush the plasmashell cache
Bug reported: https://bugs.kde.org/show_bug.cgi?id=483210