Bug 410729

Summary:	gtk menu and submenu are black on Wayland
Product:	[Plasma] kwin	Reporter:	Patrick Silva <bugseforuns>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dk.1997-fast, nate
Priority:	NOR
Version:	5.17.90
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	black "Open" menu black "Tools" submenu

Description Patrick Silva 2019-08-08 15:34:35 UTC

Created attachment 122013 [details]
black "Open" menu

SUMMARY
already reported to gtk devs
https://gitlab.gnome.org/GNOME/gtk/issues/1580

STEPS TO REPRODUCE
1. start Wayland session
2. install Gedit text editor
3. open Gedit,  click on "Open" button on top (black menu opens)
4.. click on hamburger button on top, open "Tools" submenu (black submenu opens)

OBSERVED RESULT
See the attached screenshots.

EXPECTED RESULT
gtk menu and submenu open correctly.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0

Comment 1 Patrick Silva 2019-08-08 15:35:33 UTC

Created attachment 122014 [details]
black "Tools" submenu

Comment 2 Nate Graham 2019-08-09 15:16:53 UTC

Can sort of reproduce. When I open a pop-over, it's black for a moment, but then the content appears, and immediately thereafter, then the popover's shadow gets rendered repeatedly, becoming blacker and blacker. I suspect it would crash if I don't close it.

Comment 3 Vlad Zahorodnii 2019-08-31 09:30:29 UTC

What GPU do you have?

Comment 4 Patrick Silva 2019-08-31 12:50:58 UTC

This bug occurs on two systems running on different hardwares.
computer A: Arch Linux, intel hd graphics (celeron G1820 cpu)
computer B: Neon unstable edition, intel hd 4000

Comment 5 Patrick Silva 2020-05-05 20:44:51 UTC


*** This bug has been marked as a duplicate of bug 387313 ***

Comment 6 Vlad Zahorodnii 2020-05-06 08:38:21 UTC

I don't think that it's a duplicate of bug 387313, but on the other hand I'm no longer able to reproduce this bug.