Sorry for the late reply. It should work, I think. But currently (in Plucky) we’re missing Venus firmware:
[ 5.947627] qcom-venus aa00000.video-codec: Adding to iommu group 18
[ 5.949637] qcom-venus aa00000.video-codec: non legacy binding
[ 6.003894] qcom-venus aa00000.video-codec: Direct firmware load for qcom/sc8280xp/LENOVO/21BX/qcvss8280.mbn failed with error -2
[ 6.003900] qcom-venus aa00000.video-codec: fail to load video firmware
[ 6.008167] qcom-venus aa00000.video-codec: probe with driver qcom-venus failed with error -22
Anyone found Chromium based browsers not working properly lately. About a week ago I noticed weird GUI artefacts in Brave that made it usable. I uninstalled it as don’t really use it often.
Today the same thing happened with Chromium. They seem to have started after updating the snap packages. I tried rolling back Chromium using sudo snap revert chromium but after that I just got a brief window appear and close down. Have tried reinstalling Chromium and Brave too but to no avail. Here’s what the setting page now looks like.
Well, you want to switch back from that channel later on again when the revision that is now in “edge” has moved to stable, running snaps off the edge channel long term is slightly risky given all the untested stuff lands there …
(to switch back to stable once it is ready you use:
when the revision that is now in “edge” has moved to stable
For Chromium that is not quite how the channels are used; We use upstream’s dev channel in edge, beta in beta and stable in candidate and stable. So a revision from edge does not eventually flow back into stable.
Moreover, edge has been for many months on core24 while beta and stable are on core22. And will be for some more (because we’re waiting on the resolution of a Snapd bug).
If problems are encountered on edge, you can go back to stable as Ogra suggests and then use
chromium --disable-gpu
to get rid of the artifacts until we are able to switch its base to core24 (which will solve the original issue).
