https://bugs.kde.org/show_bug.cgi?id=397082
--- Comment #18 from Michał Dybczak <michal.dybc...@gmail.com> --- Thanks for the info Filip. The fact that you have to use git versions from AUR to have fixed version from top, trendy themes, while those in repos of cutting edge distros are broken + hundreds of other themes elsewhere makes the situation very bad. And that's quite some time after the 5.13 release. I'm also a maintainer of some themes and I would like to fix them but I don't know how. I have no idea what has changed under the hood and what needs updating. As far I check, all themes do have correct media icon, but it's not showing up because of the recent changes so paths are broken somehow. If the change that broke almost all the non-breeze themes is justified, then fine, but we are waiting for official announcement and how to fix our themes. Still, most of themes will stay broken. This creates a very bad precedence where people have easy access to hundreds of themes on opendesk sites (like kde store) but no warning or info about their compatibility. We are used to that themes usually work. On Gnome breakages and hunting for versions that suit Gtk/Gnome version is normal but KDE is not prepared for it. On Gnome plugins have already notification about which version they are compatible with. Yeah, they have a mess but people learned how to deal with it. For example, Plasma themes now need some additional info like: Compatible up to Plasma 5.12; Compatible with Plasma 5.13+. Without it we either find out that effect is bad after using it or looking when the theme was changed. In latter case it doesn't even say that it was fixed for this compatibility, it may have not been. Also, users on Plasma are not use to paying attention to that kind of info. Plasma do create some compatibility breakages but they are usually under the hood, not with external, abundant third party sources as with themes. IMO the issue is huge and creates dangerous complications for user experience. The question is, was this breakage really worth it? There is a great and funny video how Linus Torvalds treats the breakage of user space: https://www.youtube.com/watch?v=FUsJ-Lr4kww Of course, kernel and Plasma desktop themes are not the same even in the slightest, but still some thought about breaking user experience must be made. Oftentimes developers have different priorities in mind and conflicts arise. Since developers have upper hand and can create change on whim, this tempts to go too far since they see a code problem, not a usability and experience problem. So once again, is this theming change so important that we should sacrifice whole desktop stack as incompatible from now on? Was there no other, smoother way to resolve it? At least with some legacy lines that uphold compatibility but allow for the change somehow? -- You are receiving this mail because: You are watching all bug changes.
