I applied this updated last Saturday. It felt as everything was OK, but today, I discovered, that trying to launch screen sharing (Wayland), Chromium browser (used for Google Meet, as it works better on it than on FF) was crashing all the time, had to switch to X11 for the moment of online work meetup.
I am also updating some packages now via pamac, and they seem to hang indefinitely in the phase of cleaning.
That is the second serious thing discovered.
I have no time to debug it, so probably will roll back and switch to stable, because this update starts showing more and more problems that were not there anymore.
I’m on stable and also having the issue (Chromium 134.0.6998.88), only happens when trying to share a window, sharing full screen or tab works. Tested in BBB and Teams. Could not find any open issue for Chromium.
Edit: Here we are: sharing a wayland desktop crashs browser / Applications & Desktop Environments / Arch Linux Forums
I’ve moved this from the Testing Updates topic to a separate thread as the issue has now reached Stable branch. At the moment, the previous posts indicate that it is only occurring on Plasma Wayland.
As well as the link posted above by @Telcoced, there is another Arch forum post about this issue: Chromium screen share crash / Applications & Desktop Environments / Arch Linux Forums
The only solution so far from the above Arch thread:
Same SIGILL error here, on a laptop with Intel i7-1165g7 CPU
Downgrading Arch package from 134.0.6998.88-1 to 134.0.6998.35-2 works
Flatpak package with version 134.0.6998.88 also works without trouble
2 Likes
Downgrade to Chromium 133.0.6943.141 helped for coworkers and me.
Problem still there with 134.0.6998.117
1 Like
The stacktrace in that forum entry helped my identify the (possible) culprit in CHROME (did not yet test with chromium, but the effects and log entries were the same).
When deactivating the “Plasma Integration” extension, the crashes no longer occur for me:
(sorry, cannot yet post a screenshot, deactivating was enough, no need to uninstall)
Could anyone verify and perhaps post that in the arch forums (don’t have an account there …)
I’ll go looking how to open a bug report for the extension …
Chromium is crashing a lot these days - I have switched to Vivaldi for that reason - I don’t care if part of it is closed source - they provide a great browser - no strings attached.
1 Like
I have this issue using Chromium (134.0.6998.165-1) with the Plasma extension disabled
Hi @mat250 , could you try completly closing/ending chromium after disabling the extension and then restarting?
Just to be sure, because that’s what I did after disabling (and forgot to mention 
)
Edit: just re-tested myself. You definitely need to restart the browser for the deactivate “Plasma Integration” to work.
Also, after re-activating it, the browser still does not crash until after the next browser-restart…
I believe you’ll need to create an account to open a bug report, so you may as well create an Arch forum account at the same time.
Regards.
@Sumpfling This is strange because after restarting the browser, I still have this issue on my side.
I stick to v134.0.6998.35-1 for now.
@mat250
It definitely helped for me, sorry top hear that it did not help for you. So, either the issue is different for chromium and chrome, or our testcases differ.
Myself, I tested with MS Teams (company …) and had either crashes or (seldom) an error message “we could not share your screen”.
Testing with https: / /mozilla.github.io/webrtc-landing/gum_test.html (sorry, cannot yet post links) on the other hand did work.
I still suspect some kind of version incompatibility with a library - that would explain the working flatpak. Perhaps your chromium “always” loads the “wrong” library and my chrome only via the plasma integration …
But that is “reading the future from tea leaves” 
1 Like
I’m just using Google Meet with FF now, and it works without problem.
2 Likes