This is an upstream issue in KDE Frameworks, but I'm reporting this here because other users coming across the issue might think it's a Chicago95 issue instead of KDE.
Upstream Report with more details: https://bugs.kde.org/show_bug.cgi?id=517534
As of Frameworks 6.23, KDE will now use an SVG icon if it exists, even if there's an appropriate-size PNG icon (previously, it was doing the opposite, but that was far less noticeable in practice). Instead of using a 16/22/32px icon, it'll use the "scalable" (which are usually 48px) icon scaled down to 16/22/32px. Because Chicago95 is 'pixel art', the result looks blurred and messy.
A temporary workaround is to comment out all of the "scalable" folders from index.theme (functionally just removing them). Not ideal, but it turns out they weren't being used properly anyway.
I noticed this with my own spinoff, but it happens with Chicago95 icons as well.
This is an upstream issue in KDE Frameworks, but I'm reporting this here because other users coming across the issue might think it's a Chicago95 issue instead of KDE.
Upstream Report with more details: https://bugs.kde.org/show_bug.cgi?id=517534
As of Frameworks 6.23, KDE will now use an SVG icon if it exists, even if there's an appropriate-size PNG icon (previously, it was doing the opposite, but that was far less noticeable in practice). Instead of using a 16/22/32px icon, it'll use the "scalable" (which are usually 48px) icon scaled down to 16/22/32px. Because Chicago95 is 'pixel art', the result looks blurred and messy.
A temporary workaround is to comment out all of the "scalable" folders from
index.theme(functionally just removing them). Not ideal, but it turns out they weren't being used properly anyway.I noticed this with my own spinoff, but it happens with Chicago95 icons as well.