Bug 472227 - certain svg icons don't display properly/only white background
Summary: certain svg icons don't display properly/only white background
Status: RESOLVED DUPLICATE of bug 448234
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Launcher (Kickoff) (show other bugs)
Version: 5.27.6
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-13 16:16 UTC by Renner03
Modified: 2023-07-24 23:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Renner03 2023-07-13 16:16:44 UTC
SUMMARY
svg icons are not displayed properly for some apps

STEPS TO REPRODUCE
1. install the 2 applications (flatpak install --user org.getmonero.Monero io.missioncenter.MissionCenter)
2. open kickoff search for the apps
3. look at the icons

OBSERVED RESULT
white background for svgs

EXPECTED RESULT
display the proper svg

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
I noticed that the flatpaks of org.getmonero.Monero and io.missioncenter.MissionCenter both just look off in the application launcher and you can only see a white background. Same is true when you open the svgs in gwenview (native and flatpak). Maybe its a problem with some underlying qt svg library?

The native package of Archlinux of monero-gui uses a png.
Dolphins preview yields the same result. However if you open the exact same file with inkscape it works like expected.

Its properly shown on GNOME (also tested on Fedora Kinoite, rebasing to Silverblue)

Path of icons:
~/.local/share/flatpak/app/org.getmonero.Monero/current/active/files/share/icons/hicolor/scalable/apps/
~/.local/share/flatpak/app/io.missioncenter.MissionCenter/current/active/files/share/icons/hicolor/
Comment 1 Nate Graham 2023-07-24 23:45:39 UTC

*** This bug has been marked as a duplicate of bug 448234 ***