> 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.
> 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 logging= stderr --v=1...
--enable-