Bug 487234

Summary: Some Breeze (light) icons not recolored for the Breeze Dark package
Product: [Plasma] Breeze Reporter: Corbin <schwimmbeckc>
Component: IconsAssignee: visual-design
Status: RESOLVED DUPLICATE    
Severity: normal CC: kainz.a, m
Priority: NOR    
Version First Reported In: 6.0.4   
Target Milestone: ---   
Platform: unspecified   
OS: All   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: breeze6 vs breeze5 (dark icons)

Description Corbin 2024-05-19 13:59:58 UTC
Created attachment 169615 [details]
breeze6 vs breeze5 (dark icons)

I'm developing an application with PySide6  (Qt for Python) and use xdg icon theme names to let my app be themeable.
This means it pulls icons from the system's icon theme, in my case, Breeze Dark.
Unfortunately, Qt doesn't natively recolor icons, so with Breeze6 I noticed that some of my icons were now from the breeze
instead of the breeze dark set.
Looking at where the icons are stored: /usr/share/icons/breeze-dark I saw that many of the icons, especially in the 
status/16 directory, weren't actually recolored, but instead identical to their breeze (light) counterpart.
Looking at the Gitlab, it's clear that there is an automated process that generates the dark icons from the light icons,
but apparently it isn't working so well, as the number of un-recolored icons has drastically increased since breeze5.

Checking the pacman cache, to look at the contents of the tar.gz that was installed, I saw much the same. 
Then checking another distro, I looked at the contents of the breeze-icon-theme-6.2.0 Fedora rpm 
(https://src.fedoraproject.org/rpms/breeze-icon-theme), which was identical. Attached is a split for the breeze 5

SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Corbin 2024-05-19 14:07:15 UTC

*** This bug has been marked as a duplicate of bug 487235 ***
Comment 2 Corbin 2024-05-19 14:08:14 UTC
A misclick of pressing enter rather than shift enter caused this to be submitted prematurely, causing a duplicate report, since these cannot be edited afterwards.