KDE Wayland, Debian Testing, Macbook Pro (Intel Iris 6100 (Broadwell GT3))

MOZ_ENABLE_WAYLAND=1 mozregression --repo autoland --good 2020-03-15 --bad 2020-03-18 --pref gfx.webrender.force-disabled:true general.autoScroll:true security.sandbox.content.level:0

8:13.07 INFO: Last good revision: d30df7470df1beaad7ea888ed77f48e5506c9f96
8:13.07 INFO: First bad revision: 1b0e41d6272316562c355f9aa6a9fe0ee191286c
8:13.07 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d30df7470df1beaad7ea888ed77f48e5506c9f96&tochange=1b0e41d6272316562c355f9aa6a9fe0ee191286c

1b0e41d6272316562c355f9aa6a9fe0ee191286c Martin Stransky — Bug 1623060 [Wayland] Respect GtkWidget size then committing to wayland surface, r=jhorak

I tested bug 1627469 comment 3 and could see window content in very rare cases. Most often it was still black.

$ pip3 install --upgrade mozregression
$ MOZ_LOG="WidgetWayland:5" MOZ_ENABLE_WAYLAND=1 mozregression --launch 2020-06-06 --pref gfx.webrender.force-disabled:true general.autoScroll:true security.sandbox.content.level:0 -P stdout &> kde-black.txt

It's most likely a kwin bug. Can you reproduce this bug with weston?

(In reply to Vlad Zahorodnii [:zzag] from comment #2)

It's most likely a kwin bug. Can you reproduce this bug with weston?

$ pip3 install --upgrade mozregression
$ MOZ_ENABLE_WAYLAND=1 mozregression --launch 2020-06-10 --pref gfx.webrender.force-disabled:true

No visible problem:

• Gnome Wayland/Debian Testing
• Weston Wayland/Debian Testing
• Weston/KDE X11/Debian Testing
• Sway Wayland/Debian Testing

Black window content:

• Plasma Wayland/Debian Testing (kwin-wayland 4:5.17.5-2)
• Plasma Wayland/Ubuntu 20.04 (kwin-wayland 4:5.18.4.1-0ubuntu2)

When I resize Firefox Nightly on Ubuntu, the actual window content is shown for a part of a second (it flickers), then it's black again.
(Resizing on Debian Testing is buggy as it doesn't have the fix for bug 1593478. Plasma is too old here.)

I had forgotten to update Ubuntu 20.04: kwin-wayland 4:5.18.5-0ubuntu0.1 is affected as well.

Okay, it seems like that's our bug. Could you please file a bug report on bugs.kde.org?

Should be already fixed.