Summary: | Regression: Using a non-Breeze icon theme results in mixed non-Breeze + Breeze icons. | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Paul <pip.kde> |
Component: | kcm_icons | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | cameronpoe, opensuse.lietuviu.kalba, unassigned-bugs, wbauer1 |
Priority: | NOR | ||
Version: | 5.4.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot showing mixed "Oxygen Ionised" and "Breeze" Icons
mixed icons in KDE Plasma 5.4 Mixed icons in KDE Plasma 5.5.0 |
Description
Paul
2015-11-29 10:34:28 UTC
Created attachment 95798 [details]
Screenshot showing mixed "Oxygen Ionised" and "Breeze" Icons
*** Bug 356423 has been marked as a duplicate of this bug. *** Please for non-Breeze themes respect specifications: according http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html , the default fallback icon theme must be "hicolor". I.e. as fallback, please use /usr/share/icons/hicolor/ and /usr/share/pixmaps Created attachment 95951 [details]
mixed icons in KDE Plasma 5.4
Created attachment 95953 [details]
Mixed icons in KDE Plasma 5.5.0
I have the same problem on openSUSE 42.1 with Plasma 5.5.4 when updated framework from 5.16.0 to 5.19.0. It was OK on 5.16.0 in my Plasma 5.5.4. (In reply to opensuse.lietuviu.kalba from comment #3) > Please for non-Breeze themes respect specifications: > according > http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html > , > the default fallback icon theme must be "hicolor". > I.e. as fallback, please use /usr/share/icons/hicolor/ and /usr/share/pixmaps Actually the fallback is "hicolor". If you delete the corresponding breeze icon, the one from hicolor is taken then. It's "just" that "breeze" seems to be used as fallback additionally, and preferred over the real fallback, hicolor. But yes, still a bug (I suppose). Please see this bug report: https://bugs.kde.org/show_bug.cgi?id=360664 for the reason behind this behaviour. Let's mark it as duplicate then... *** This bug has been marked as a duplicate of bug 360664 *** |