(In reply to Michel Dänzer from comment #12)
> Does this still happen with current versions of the graphics stack, in
> particular libxcb 1.11.1 or newer?
An Arch user complained to me about this bug just last month, and the LIBGL_DRI3_DISABLE=1 trick "fixed" the issue for him. I see libxcb 1.11.1 has been in Arch since September, so it seems extremely likely that he was using it at the time.
The issue is 100% reproducible on any DuckDuckGo search results page (e.g. [1]) when DRI3 is enabled on a wide variety of hardware. However, my distro of choice, Fedora, has disabled DRI3, and therefore I am personally no longer able to easily reproduce.
(In reply to Michel Dänzer from comment #12)
> Does this still happen with current versions of the graphics stack, in
> particular libxcb 1.11.1 or newer?
An Arch user complained to me about this bug just last month, and the LIBGL_DRI3_ DISABLE= 1 trick "fixed" the issue for him. I see libxcb 1.11.1 has been in Arch since September, so it seems extremely likely that he was using it at the time.
The issue is 100% reproducible on any DuckDuckGo search results page (e.g. [1]) when DRI3 is enabled on a wide variety of hardware. However, my distro of choice, Fedora, has disabled DRI3, and therefore I am personally no longer able to easily reproduce.
[1] https:/ /duckduckgo. com/?q= freedesktop& t=epiphany& ia=about