On 2023-06-12, Grant Edwards <grant.b.edwa...@gmail.com> wrote:
> I did an update this morning which installed the following:
>
> aleph ~ # fgrep '>>> emerge ' emerge.log
>
> 1686579407: >>> emerge (1 of 11) dev-util/strace-6.3 to /
> 1686579455: >>> emerge (2 of 11) dev-libs/nspr-4.35-r2 to /
> 1686579470: >>> emerge (3 of 11) dev-python/fonttools-4.39.4 to /
> 1686579500: >>> emerge (4 of 11) dev-python/weasyprint-59.0 to /
> 1686579507: >>> emerge (5 of 11) net-print/cups-2.4.4 to /
> 1686579541: >>> emerge (6 of 11) sys-devel/llvm-15.0.7-r3 to /
> 1686582174: >>> emerge (7 of 11) app-portage/gemato-20.4 to /
> 1686582180: >>> emerge (8 of 11) media-libs/gstreamer-1.20.5 to /
> 1686582206: >>> emerge (9 of 11) dev-db/unixODBC-2.3.11 to /
> 1686582239: >>> emerge (10 of 11) media-libs/gst-plugins-base-1.20.5 to /
> 1686582282: >>> emerge (11 of 11) www-client/firefox-bin-114.0.1 to /
>
>
> Now google-chrome-stable Version 114.0.5735.106 (Official Build)
> (64-bit) can lo longer display pages proplerly. It looks like chunks
> of the application window are randomly scrambled or shown in the wrong
> places. AFIACT, the pages are being parsed/process properly but the
> actaul rendering of the X11 window is broken.
It seems to be a variation on this bug which affects only AMD GPUs:
https://bugs.gentoo.org/907431
Clearing the GPU driver cache or using the -disable-gpu-driver-bug-workarounds
option avoids the problem.
In my case, It wasn't a mesa update that triggered the problem. I
think it was the llvm update (I haven't confirmed that).
--
Grant
