After Mesa upgrades, Chrome won't show graphics
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Lunar |
Invalid
|
Undecided
|
Unassigned | ||
mesa (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Invalid
|
Undecided
|
Unassigned |
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-
[UPGRADE] libegl1-mesa:amd64 22.2.5-
[UPGRADE] libgl1-
[UPGRADE] libgl1-
[UPGRADE] libglapi-mesa:amd64 22.2.5-
[UPGRADE] libglx-mesa0:amd64 22.2.5-
[UPGRADE] mesa-vulkan-
We documented the problem in AskUbuntu before we realized it was probably related to Mesa, so wanted to link to that report here:
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.
description: | updated |
affects: | ubuntu → mesa |
affects: | mesa → mesa (Ubuntu) |
Changed in mesa (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
description: | updated |
Changed in chromium-browser (Ubuntu): | |
importance: | Undecided → High |
tags: | added: jammy regression-update |
Changed in mesa (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
summary: |
- After mesa upgrades, Chrome won't show graphics + After Mesa upgrades, Chrome won't show graphics |
description: | updated |
Changed in chromium-browser (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in chromium-browser (Ubuntu Lunar): | |
status: | New → Invalid |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/2020604/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]