Closing due to this bug's age, and it being an upstream issue.

The upstream bug was resolved in Plasma 5.27 via https://bugs.kde.org/show_bug.cgi?id=414559

As an update for anyone not following Budgie spaces, this has been fixed upstream and a new release should be made shortly fixing all the workspace applet issues.

This is an upstream issue, we have to wait till it get fixed there

Should be filed with AMD. https://gitlab.freedesktop.org/drm/amd/-/issues

Thanks for your report. Please file this upstream with the Intel graphics team so they can best review your issue. I would suggest providing the information reported via inxi -CGxx though, as well as the kernel you are using uname -a, as that will provide more meaningful information that the videos and screenshot of the hardware info, although the videos will be useful for them in visualizing your issue.

Please file your issue with AMD, as they will be best equipped to resolve your issue.

Apologies. That was a separate issue.

I believe I saw that @kyrios123 was looking into this. Assigning since he is the MATE maintainer.

This should be reported upstream to the MATE project. We don't do anything special here.

This should be reported at https://bugzilla.kernel.org

Not planning on downgrading librsvg however, as I need ABIs for EFL that are in 2.51.x and above.

I opened an issue at GNOME's gitlab: https://gitlab.gnome.org/GNOME/librsvg/-/issues/797

Updated on GitHub, but this is almost certainly a bug with librsvg rather than numix-icon-theme; the height and width attributes are optional in the SVG spec (default 100%, with us controlling size via viewbox). We can add a width attribute to any SVG file missing them in Numix to work around the problem for now, but that should only be a temporary fix until librsvg fixes whatever the problem is on their end.

The root cause has been determined upstream. The file /usr/share/icons/Numix/scalable/actions/system-shutdown-symbolic.svg apparently was missing a width attribute, and all of a sudden that seems to have become a problem with librsvg-2.52.0. See: https://github.com/numixproject/numix-icon-theme/issues/1405.

@JoshStrobl ?

Thanks @pillmuncher for filing the issue upstream at https://github.com/numixproject/numix-icon-theme/issues/1405

@algent: Thank you so much. That fixed it for me, too. I've opened an issue on the Numix github: https://github.com/numixproject/numix-icon-theme/issues/1405

@JoshStrobl I found that the issue is with librsvg.
I downgraded librsvg from 2.52.0 to 2.50.7 and rebuild adwaita-icon-theme version 41.0 against it.
Then installed adwaita-icon-theme. After this system-shutdown-symbolic.svg icon from Numix theme is loading fine.

Sorry, by "missing" I didn't mean to say "missing in the file folders", but "icon file exists, but icon isn't shown on the panel".

In T9920#188381, @JoshStrobl wrote:

Is this an issue with our packaging of numix itself? Given the discussion on the forum post.

@algent Is this an issue with our packaging of numix itself? Given the discussion on the forum post.

This should really be reported to the respective icon theme developers. They need to add the icon, it isn't on Solus (or Budgie for that matter).

Tried a few things to maybe get it to work still, but unfortunately without success. Will keep an eye on it in case a solution surfaces, but looks like it might actually be best to give up on it.

Patched fifengine but this package is still completely borked. Read AUR comments: https://aur.archlinux.org/packages/unknown-horizons

In T9839#186886, @JoshStrobl wrote:

Upstream issue:

• https://bugs.kde.org/show_bug.cgi?id=431302
• https://bugs.kde.org/show_bug.cgi?id=426174
• https://bugs.kde.org/show_bug.cgi?id=434076

I'll file an issue on their bugtracker. Downgrading kdeconnect to 21.04.3-42 seems to work as a workaround for now.

Ah, thanks for the clarification. Seeing as this is specific to KDE Connect, I would suggest filing an issue on their development tracker. Going to mark it as an upstream issue.

Thank you for the test @chax.

Yes, it works now.

In T8287#187079, @algent wrote:

A patch was submitted to fix this issue upstream. I packaged this again but need help by someone who had this issue.
You can find the eopkg files here shared with google drive.

Please test.

A patch was submitted to fix this issue upstream. I packaged this again but need help by someone who had this issue.
You can find the eopkg files here shared with google drive.

Upstream issue:

In T9700#186421, @szmarczak wrote:

When can we expect this to land in Software Center?

When can we expect this to land in Software Center?