Bug 360742

Summary: Customization of Plasma Workspace Themes not possible
Product: [Plasma] plasmashell Reporter: Florian Röhrer <florian.roehrer>
Component: Desktop ContainmentAssignee: Sebastian Kügler <sebas>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, pip.kde, samrog131
Priority: NOR    
Version: 5.5.95   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Florian Röhrer 2016-03-19 16:46:09 UTC
Since the last update, the possibility to customize plasma themes is missing. For example i can not chose a theme and modify it to use the taskbar background from another theme. You can see which settings i mean in the following screenshot:

https://www.dropbox.com/s/x1reefgv9pyflt0/plasmatheme.png?dl=1

Those settings are no longer present.

Reproducible: Always
Comment 1 Paul 2016-03-19 17:52:33 UTC
See this review request:
https://git.reviewboard.kde.org/r/126953/

Which contains the following quote from "Marco Martin"
"I always wanted to kill that thing!
I was a bit scared of the potential reaction.."

I was also somewhat disappointed at it's demise... :(
Comment 2 Florian Röhrer 2016-03-19 18:13:51 UTC
Is there any possibility to get this functionality back. I really love this feature because most of the available themes are not really nice at all. In every theme i want to change something and i dont want to edit each theme manually. I am really sad to say that i have to think about a desktop change if this feature does not come back because i want a beautiful and customizable desktop. That is what i always loved about KDE.... :(
Also i do not see any reason to remove this feature. People who do not want to use it don't have to.
Comment 3 Rog131 2016-03-19 18:26:45 UTC
This is seems to be a dublicate of the  Bug 359127 - Desktop theme KCM 'details' and editing tab no longer present/functional  - https://bugs.kde.org/show_bug.cgi?id=359127

It's status is 'RESOLVED WONTFIX'
Comment 4 Kai Uwe Broulik 2016-03-20 11:08:59 UTC

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