Bug 438639

Summary:	Plasma themes can replace shell icons even if they are disabled
Product:	[Plasma] plasmashell	Reporter:	Podagric <kde.podagric>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.22.0
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Podagric 2021-06-14 17:48:36 UTC

STEPS TO REPRODUCE
1. In systemsettings, go to the option to download new plasma themes and search for fluent dark plasma (https://store.kde.org/p/1499867/) and install it
2. Apply the theme and then go back to breeze

OBSERVED RESULT
The systray icons, widgets and applets will continue with the fluent dark stuff even if it is disabled.

ADDITIONAL INFORMATION
As I understand it, this is happening because the theme is installed in `~/.local/share/plasma/desktoptheme/default` and has priority over `/usr/share/plasma/desktoptheme/default/

After renaming it to anything other than `default`, this bug no longer happens.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Graphics Platform: X11

Comment 1 Nate Graham 2021-06-15 21:15:58 UTC

You're probably right, but this seems like a really bad bug in that theme. Naming itself "default" is super bad. Can you please contact the theme's developer and ask them to fix it?

Comment 2 Podagric 2021-06-15 23:30:49 UTC

Yes, it will certainly solve that, but the point is that any developer can forget to rename a folder and end up generating the same bug, and less experienced users who install the theme will have this problem without knowing why.
It took me a while to understand what was going on. It was very irritating.
I'm sorry but nothing is resolved at the moment.

Comment 3 Nate Graham 2021-06-15 23:56:56 UTC

In this case "resolved downstream" means "it's somebody else's fault. Yes, if the developer of a theme is careless, their subpar work can mess up your system. This is always the risk you take when using 3rd-party software. Some of it is better, and safer, and stabler than others. In all cases, the outcome is the same: report the bug to the developer who is causing it. :)