[systemsettings] [Bug 356064] New: Non Breeze themes now display some Breeze icons.
Paul via KDE Bugzilla
bugzilla_noreply at kde.org
Sun Nov 29 10:34:28 GMT 2015
https://bugs.kde.org/show_bug.cgi?id=356064
Bug ID: 356064
Summary: Non Breeze themes now display some Breeze icons.
Product: systemsettings
Version: 5.4.3
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kcm_icons
Assignee: unassigned-bugs at kde.org
Reporter: pip.kde at gmx.com
CC: unassigned-bugs at kde.org
When using a non Breeze icon theme, Oxygen or Adwaita for example, there are a
mix of the selected theme icons and Breeze icons; as shown in attached
screenshot of the Application Menu. Although it is not restricted to that, I'm
also seeing the effect in, for example Dolphin, where a lot of the mime type
icons are the Breeze variants.
Reproducible: Always
Steps to Reproduce:
1. Use "System Settings -> Icons -> Theme" to select and apply a non Breeze
Theme.
2.
3.
Actual Results:
The selected theme displays part Breeze icons.
Expected Results:
The selected theme does not display Breeze icons.
System Settings:
Version 5.4.3
KDE Frameworks 5.16.0
Qt 5.5.1 (built against 5.5.1)
OS:
Tumbleweed snapshot 20151124
note: this snapshot contained the kde-frameworks version update 5.15.0 ->
5.16.0
The Icons set I normally use is "Oxygen Ionised" (user theme located at
~/.local/share/icons)
This is not restricted to that Icon set, "Oxygen" and "Adwaita" also exhibit
this behaviour.
It is not caused by missing Icons from the "Oxygen Ionised", "Oxygen" or
"Adwaita" themes. Also, in the case of "Oxygen" variants the theme inherits
"hicolor", not "Breeze".
It is not a cache issue. Deleting "icon-cache.kcache" (from a VT whilst not
logged in to KDE), does not "solve" the problem.
It is not unique to a single user. Creating a new user (which initially has the
default "Breeze" icon theme) and changing to "Oxygen" or "Adwaita" exhibits the
same "mixed" theme.
Prior to the kde-frameworks version update 5.15.0 -> 5.16.0 this problem did
not exist.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list