Created attachment 151535 [details] Example using a not-yet-released version of the Nova7 icon theme SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install a theme which uses a design with gradients and/or multiple colours for the icon change-date-symbolic. It does not matter whether the icons are saved as png (fixed) or svg (scalable). 2. Go to system settings > appearance 3. Open any of the subcategories which feature a download option (e.g. colours or icons) 4. Click the 'Get New...' button 5. Click the 'Recent' drop-down menu OBSERVED RESULT The icon for 'Show most recent first' will always display as a solid black surface with no gradients; irrespective of whether the icon file used is a png or svg vector image. EXPECTED RESULT The icon is displayed as intended by the artist. Note: the reason why I am filing this as a bug is twofold: - The same behaviour does not apply to the other icons in the same drop-down menu: these all display correctly; - The same icon (change-date-symbolic) is used for the 'Recent' button itself, where it does display correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I suspect this has not been noticed thus far since the Breeze 'change-date-symbolic' icon uses a solid black design without any gradients. I also wonder what the guidelines for using 'symbolic' icons are. The only information I have been able to find on 'symbolic' icons was on this page for the Gnome, not KDE project: https://wiki.gnome.org/Design/OS/SymbolicIcons. The reasons for using 'symbolic' icons listed on that page do not appear to apply here. What is more, none of the other entries in this drop-down menu use 'symbolic' versions of regular icons.
*** This bug has been marked as a duplicate of bug 451538 ***
Thanks, Nate Graham! I wasn't able to find other instances of this bug myself.