This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.3
---------------
mesa (22.2.5-0ubuntu0.1~22.04.3) jammy; urgency=medium
* rules: Set VERSION so that it also includes the packaging
revision. (LP: #2020604)
-- Timo Aaltonen <tjaal...@debian.org> Wed, 31 May 2023 11:21:54 +0300
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After Mesa upgrades, Chrome won't show graphics
Status in chromium-browser package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Fix Released
Status in chromium-browser source package in Jammy:
Invalid
Status in mesa source package in Jammy:
Fix Released
Status in chromium-browser source package in Lunar:
Invalid
Status in mesa source package in Lunar:
Invalid
Bug description:
[Impact]
After patching Mesa with some driver updates, Chromium/Brave started seeing
corrupt graphics. This was due to GPU acceleration being enabled in the browser
by default now, and the old GPU shader cache is invalid in some ways and the
browser is not able to recognize that the driver has changed, since the
upstream version string hasn't changed. This is shown for instance with
'glxinfo -B' or under 'chrome:gpu' from the browser.
The fix is to make the upstream VERSION to have the full packaging
version, this will then be used for the core profile version string as
well.
[Test case]
- run stock jammy, install brave-browser from brave.com, launch brave-
browser, check that 'brave://gpu' shows things are accelerated, then
exit the browser
- enable proposed, install libgl1-mesa-dri et al
- launch brave-browser again, verify that gfx are not corrupted and
brave://gpu is showing acceration being used
with the pulled update, graphics would be severely corrupted
[Where things could go wrong]
There could be apps that expect the Mesa version string to only contain
a.b.c, and break in some ways when that's no longer the case.
--
After today's Ubuntu 22.04 Mesa upgrades many of our users reported
problems viewing graphics when using Google Chrome (Stable).
The Mesa upgrades we installed were:
[UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
[UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 ->
22.2.5-0ubuntu0.1~22.04.2
We documented the problem in AskUbuntu before we realized it was
probably related to Mesa, so wanted to link to that report here:
https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
updates-chrome-wont-display-website-graphi
There are several useful pointers and bypasses listed in that
AskUbuntu link (one being to remove affected users' GPUCache
directories, which does not destroy their profiles and seems to work
in many but not all cases).
Not sure if this is an issue with Mesa or Chrome or specific machine
graphics or an interaction between them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
