Comment 23 for bug 2020604

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 several chromium based browsers.

On 5/26/23 11:14 AM, Nathan Teodosio wrote:
>> 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 read  the url. A real chicken and egg
>> problem.
> One could do a blind
>
> Ctrl+L
> about:gpu<Enter>
> <Tab>
> <Space>
>
> to get the report to clipboard, but you would never know that without
> seeing the page. (:
>
> That information isn't otherwise available even with
> --enable-logging=stderr --v=1...
>