For any Linux Mint 21.1 users... their systems may be behind in getting
updates. But in the last few days I've had some users experience this
problem with Google Chrome (Version 114.0.5735.198) and with Brave
(Version 1.52.130). Thanks to posts here these fixes worked for me:
Chrome:
Delete
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 Wed, 31 May 2023 11:21:54 +0300
** Changed
marking invalid for lunar as it's not currently affected, and the next
upload will bump to latest upstream version and also change the string
to address this bug, but no need to verify that one for lunar
** Changed in: mesa (Ubuntu Lunar)
Status: Confirmed => Invalid
--
You received this
What's up with the lunar task that is still open? Lunar didn't have a
mesa update yet, so it can't have regressed. I understand if we want to
avoid future regressions in lunar too, of course, but the fix ("set
VERSION so that it also includes the packaging version") should be
bundled together with
marking verified according to #37, and also my testing shows it working
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This bug was fixed in the package mesa - 23.0.3-0ubuntu2
---
mesa (23.0.3-0ubuntu2) mantic; urgency=medium
* rules: Set VERSION so that it also includes the packaging
revision. (LP: #2020604)
-- Timo Aaltonen Tue, 30 May 2023 09:53:55 +0300
** Changed in: mesa (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Following Timo's instructions, aptitude upgraded those two packages
(along with three additional packages aptitude auto-selected) on one
test system:
[UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.2 ->
22.2.5-0ubuntu0.1~22.04.3
[UPGRADE] libgbm1:amd64 22.2.5-0ubuntu0.1~22.04.2 ->
just enable proposed, run 'apt install libgl1-mesa-dri libegl-mesa0' and
you should get all relevant updates for mesa and nothing else
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
OK just a question about pinning since we would prefer to minimize
changes to user systems. When we follow the instructions from Steve's
message on:
https://wiki.ubuntu.com/Testing/EnableProposed
which sets the pin priority for proposed to 400, the page says to run a
simulated apt upgrade to
forget about those test failures, they're flaky by nature
--
You received this bug notification because you are a member of Desktop
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
Okay we'll wait for a later build.
--
You received this bug notification because you are a member of Desktop
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
Thank you very much Steve (and Timo and everyone else that has helped).
We will test it on a few systems this weekend.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
Hello Sam, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
That's correct, but so far llvm updates have been done in tandem with
mesa backports, so I'm not too worried about those this time.
The upstream solution should take that into account, though.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I believe the same thing can likely happen if llvm updates but mesa
stays the same. Can you embed both into the string?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
For the lack of confirmation of #20 and since this is going to be
addressed in Mesa itself, I'm removing the workaround I had added to
Chromium.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of
** Description changed:
+ [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
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: chromium-browser
oh well, chrome still segfaults on startup even with that one, although
GL_RENDERER has changed now
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After Mesa upgrades,
I've got a proposed fix to mangle PACKAGE_VERSION to use the full
packaging version instead of just upstream x.x.x. It's available now on
ppa:tjaalton/test
To verify if that works, you'd need to run chrome/chromium with the
current version in -updates first (...22.04.1), then update to the ppa
** Summary changed:
- After mesa upgrades, Chrome won't show graphics
+ After Mesa upgrades, Chrome won't show graphics
** Description changed:
- After today's Ubuntu 22.04 mesa upgrades many of our users reported
+ After today's Ubuntu 22.04 Mesa upgrades many of our users reported
problems
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
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 Desktop
Packages, 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 Desktop
Packages, which is subscribed to
> Any idea if the mesa driver
> problem will be addressed in the next update?
Time will tell, if my reading of #12 is correct then this isn't really a
problem with Mesa but with upstream.
> An ironic thing about the about://gpu url is that unless you disable the
> gpu, it's not possible to even
Disabling gpu solved the problem for both Brave, Brave-beta and Chrome.
Once I could get the browsers to open up and render text, it was than
possible to turn off hardware acceleration. Any idea if the mesa driver
problem will be addressed in the next update?
An ironic thing about the
also, hardware acceleration in chromium is not enabled by default AIUI,
but it is enabled in the recent beta snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
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
`rm -R ~/.config/google-chrome/Default/GPUCache` (and then restarting
chrome) from the askubuntu post fixed it!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After mesa
** Description changed:
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
While it's obviously not a real fix, As I don't use chrome as my primary
browser, simply regenerating my ~/.config/google-chrome/ directory
resolved this issue. Others may not have this option.
Question 1 : What is it about the Mesa upgrade that kills chrome but not
Firefox?
Question 2 : Is
--disable-gpu-driver-bug-workarounds did not work for me, but deleting
GPUCache did. Keep in mind that GPUCache could be inside a profile
folder like ~/.config/google-chrome/Profile 1/.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
--
You received this bug notification because you are a member of Desktop
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 mesa package in Ubuntu:
Confirmed
Bug description:
After
I confirm the issue on a ThinkPad T440
Intel® Core™ i5-4300U CPU @ 1.90GHz × 4
Mesa Intel® HD Graphics 4400 (HSW GT2)
As a workaround I have renamed GPUCache folder for both chrome and brave
browser.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I confirm the issue on a desktop with Intel HD Graphics 530 (rev 06)
(Core i7-6700 CPU).
At present time I found that it can be worked around in two ways:
1) Using the '--disable-gpu-driver-bug-workarounds' option:
# google-chrome-stable --disable-gpu-driver-bug-workarounds
2) Defining
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
** Project changed: mesa => mesa (Ubuntu)
--
You received this bug notification because you are a member of Desktop
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 mesa package in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
39 matches
Mail list logo
