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?

Note, this should be fixed by D11489

This is an upstream Firefox issue that is not specific to MATE, or even Linux for that matter (it can happen under Windows, or Budgie as an example). The Downloads window will on many instances insist on being the foreground window.

Note that this should be fixed in the latest Nvidia beta driver (470 series).

Would like to mention if 21.1.3 doesn't resolve it, we can just try reverting both

Mesalib 21.1.3 is out and changes the respective code, it isn't immediately obvious whether or not they're still using SI_CONTEXT_PFP_SYNC_ME. I checked the SI_OP_SYNC and SI_COHERENCY enums, alongside si_get_flush_flags which is what they use to get the coherency enum to flags. It's possible SI_COHERENCY_SHADER is an equivalent and choosing another ENUM might help, but they have basically no documentation on it, soooo.

For what it's worth, I have experienced this issue too whenever I have had to set up my triple monitor setup. Generally works fine if I gradually add monitors to my configuration then export the xorg config to the appropriate location. But regardless, not a Solus-specific issue and thus marking as inavlid.

this is still not working. without a working patch, or akonadiconsole you might as well drop the entire kdepim, kmail is affected as well if im not mostaken. and its been broken forever, i doubt they will ever fix it.
an example of the type of calendar i want to add https://ics.ecal.com/ecal-sub/5fd23feb56a9ca5e018b45b9/English%20Premier%20League.ics
its simply not doable

OK, I think we can close this then. My only question was "Is there something we can do to improve the Firefox hardware acceleration story for Solus users" and the answer is "No because video hardware acceleration is a non-standardized/buggy mess".

@JoshStrobl Would you mind backporting the MimeType patch when you update Go to 1.16.3, now that it has landed upstream? That would mean backporting my patch https://github.com/golang/go/commit/3e8ba91275cdeb0af4c8b30f9cc788fd42cfbbd3 and https://github.com/golang/go/commit/7b19fb1d560908a848e07e091fb5df61f4848389 (for a bug fix making it work better on other Linux distros).

Sorry for it taking such a long time, I have been quite busy. I now have a PR up for Go that properly fixes this issue and makes mimetype lookup work on Solus: https://github.com/golang/go/pull/45271

I asked nathan when it's going to be fixed but it seems a fix is incoming :)

I filed it here as I believed this to be a matter of configuration of the package, not an issue of tracker3 itself.
However, I saw that for example Arch just places them inside /usr/lib/tracker3/ which is shared between the two packages, so maybe tracker3 does not support having different folders at all.
Would this approach be possible on Solus?

This should be filed on the kernel development tracker, they're the ones that will be able to properly diagnose and resolve this issue: https://bugzilla.kernel.org

I'm not gonna add a package just to use it as a workaround, this should be fixed upstream. I saw someone added a patch instead of upstreaming it to gitlab, well he isn't sure if this is the correct way to fix this, so I try to get in touch with the kdepim-runtime devs to get this upstreamed or get a correct patch to backport it.

This is an upstream drm/amd issue, there are countless issues reported at https://gitlab.freedesktop.org/drm/amd/-/issues such as:

https://bugs.kde.org/show_bug.cgi?id=430610 not gonna revert framework but gonna have an eye on it if I can backport something

Oh, this is my task. I guess I'll take the initiative :P

This can definitely be closed. They fixed it in framework 5.74 and we're now on 5.77.

Does appear to be this bug. If I boot without the external monitor connected and then plug it in when I'm at the sddm login in, I can log in as usual with newest kernel installed.

Given you're on nouveau, this is an upstream issue that specifically affects using sddm, noueavu, and 5.9+. It's been filed upstream and only seems to affect multi-monitor scenarios:

Alright then. Will do so :)

We're not going to have neither of those files because it shouldn't be used at all (e.g. for by normal desktop applications, which is the primary target of Solus), you don't need httpd/nginx for anything unless:

Well it's an upstream issue and as mention inside the bug report no way to backport it so you have to wait for plasma 5.20 hits the repo

Problem has been fixed with latest update to 1.35.1-57-1-x86_64

Files is Nautilus, developed by GNOME. It is likely that is either an upstream issue, or was an upstream issue. We used an older version in order to provide desktop icons support in Budgie, as noted in numerous places across our bug tracker, and a new implementation is currently in progress. Marking this as invalid as there are no actionable items for this, any fix would need to be upstream in Nautilus (and likely isn't an issue in the first place) and we're holding our Nautilus back anyways.

1st workaround - switching to strongswan works properly.

@g66925 As your link mentioned, you can try switching to strongswan. You can do that with the following commands:

Thx! I did update:

@g66925 Just so you know, the patches have been landed. You should be able to find them in the unstable repo now.

@g66925 They have not been landed. It would be better if you test them and verify that they work as expected before landing these patches. If you feel comfortable, I can build these packages and send the resulting eopkg file for you to test. It is also understandable if you prefer to build it yourself. In the latter case, you can download the aforementioned patches and build them locally. This is a very good introduction to setting up solbuild: https://www.youtube.com/watch?v=rlPnHjUBpJ8

I need a bit of support. I did not found relevant packages in unstable repo, so I presume that I should build them by myself?

@g66925 D9261 and D9262 are relevant patches aiming to fix this issue. Can you try them out?

In T8916#174749, @JoshStrobl wrote:

There's nothing we can do about this

There is. Explained right in the first post. However, I can just build 13.0 myself like I've done so far. I just wished this could've been worked around which would benefit other people who use PulseEffects.