I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice.
I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64).
My hardware is a Ryzen 5 2400G APU with vega graphics.
The issue goes away if I start the application with this variable: LIBGL_ALWAYS_SOFTWARE=1.
I've bisected the issue, here is the bad commit:
[diego@archtest mesa]$ git bisect good
1b25d340b791ad8350bdfb27f1a91ac79fa17748 is the first bad commit
Author: Sonny Jiang <email@example.com>
Date: Mon Dec 3 12:36:33 2018 -0500
radeonsi: use compute for resource_copy_region when possible
v2: marek: fix snorm8 blits
Signed-off-by: Sonny Jiang <firstname.lastname@example.org>
Signed-off-by: Marek Olšák <email@example.com>
:040000 040000 2c64a549c6512a622312f0a5955cafc17c99ae91 7615411b88672f53247c0393d28898672d8f49e1 M src
Created attachment 143894 [details]
Mesa was installed to /usr/local.
/usr/local/lib was added to /etc/ld.so.conf.d/mesa.conf.
libgbm, libEGL is being loaded from /usr/local/lib and radeonsi_dri.so is being loaded from /usr/local/lib/dri.
LLVM 7.0.1 was used to compile mesa.
Created attachment 143895 [details]
Screenshot showing the problem
Notice the lack of the "Help" menu item.
Created attachment 143896 [details]
Screnshot without the issue
GIMP started with LIBGL_ALWAYS_SOFTWARE=1 so it doesn't present the issue.
Arch Linux (x86_64)
- I've downgraded llvm8 to llvm7 before I bisected because mesa-18.3.5 required llvm7.
- Xephyr was used when I bisected (I ran GIMP inside Xephyr -glamor :1), the issue can also be reproduced with Xorg.
(In reply to Diego Viola from comment #0)
> The issue goes away if I start the application with this variable:
As discussed on IRC, presumably this would have to be set for the X server process, not the application.
Can you attach an apitrace of reproducing the problem in Xephyr?
Created attachment 143899 [details]
To reproduce it:
$ apitrace replay Xephyr.trace -w
I used apitrace 7.1-3.
I get the same problem with GNOME 3.32 on archlinux (Wayland and GNOME Xorg).
The bug has nothing to do with compute. The compute blit removed gfx-based blits from the gfx pipeline, which uncovered a bug in the driver.
(In reply to Marek Olšák from comment #10)
> The bug has nothing to do with compute. The compute blit removed gfx-based
> blits from the gfx pipeline, which uncovered a bug in the driver.
I tested your patches from this series:
and my issue is fixed after applying your patches, thank you. :D
Fixed by 440135e5a0d178c537db3f96e6823bc8220a0f3f. Closing.