Comment 17 for bug 2020604

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 about://gpu url is that unless you disable the
gpu, it's not possible to even read  the url. A real chicken and egg
problem.

Chris Hall

On 5/26/23 4:13 AM, Nathan Teodosio wrote:
> Passing --disable-gpu would likely help here.
>
> Hardware acceleration stuff can be seen in about://gpu.
>
> At the moment we have hardware acceleration decoding, which as far as I
> can tell is not the issue here, in candidate/hwacc and edge/hwacc but
> that is focused at Intel.[1]
>
> For the time being I think for Chromium snap we can just add a
>
> rm -r "$SNAP_USER_COMMON"/chromium/*/GPUCache
>
> as a stop gap measure.
>
> [1] https://discourse.ubuntu.com/t/chromium-hardware-accelerated-build-
> for-intel-based-platforms-available-for-beta-testing/35625/3
>