Well, on one of my machines I installed Mesa from the kisak more stable
ppa ("turtle"), which is more up to date than mesa from the jammy
repository. I was able to re-enable hardware acceleration with no
problems. So there is something in the whole collection of mesa packages
that broke
It seems a way that this may be avoided is for GL_RENDERER string to
always be updated when mesa updates.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After mesa upgrades,
As I have multiple profiles, I chose to simply delete all Cache
directories
$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
The workaround is available in candidate channel (currently only ready
for amd64).
snap refresh --candidate chromium
If someone could please verify the workaround, I can bump to stable.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
I'm setting the importance to Critical per
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Tags added: jammy regression-update
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
**
seems like this is a generic issue with chromium not being able to
invalidate the gpucache when the GL_RENDERER string changes, which is
every time Mesa is updated
** Package changed: mesa (Ubuntu) => chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of
6 matches
Mail list logo
