Fullscreen broken after BO handle table

[sjnewbury]

Since 5dfaf5e fullscreen (super-f) is broken for fullscreen (OpenGL?) surfaces.

AMD POLARIS10 current git mesa/wlroots/sway etc

For example Alacritty appears to display the wrong area of memory

glmark2-wayland is severely corrupted but the tests are kind of visible

Having wdisplays running makes fullscreen work (perhaps due to the overview thumbnail)

Firefox just works though

Proton DXVK and gallium-nine games show corruption when switching to fullscreen, but after creating a vulkan/nine buffer work okay.

Reverting 5dfaf5e makes everything work again.

[frmonteiro]

Are you using the latest commit?

[sjnewbury]

Are you using the latest commit?

I was when I submitted the report. The revert did need manual merging after recent changes, but it was minor and still fixed the behaviour.

[alexarice]

Just to add to this, I am having the same problems but firefox also doesn't work for me. I get green artifacts all over the screen when fullscreening any firefox video (e.g. youtube video)

[ms178]

@alexarice Did it look something like the following? I did encounter that bug as of last weekend when trying out kwinft-git with wlroots-git. At first I thought it was an LLVM14-related bug in mesa, but this could be very well the same bug as mentioned here. The bug only showed in OpenGL apps (that screenshot is from Chrome with --use-gl=desktop), RADV-games were working fine though. But also other OpenGL apps were broken, even the KDE Plasma menues flickered with that pattern when navigating in the menue.

[Xyene]

That looks similar to what I get. The issue goes away if I e.g. open a layer-shell instance like rofi on top of the fullscreen surface, then returns when rofi closes. It also doesn't happen for all apps, so maybe it's related to direct scanout? waves hands vigorously

Note that I'm not able to screenshot the issue; it appears fine in screenshots.

[alexarice]

My error looked a lot more colourful than that. I also cannot screenshot it.

I observed it happening on firefox, alacritty, and emacs, but think it happened on everything for me. I also bisected it down to the commit in the original post of this issue.

[sjnewbury]

@alexarice Mine was also more colourful. I think firefox possibly isn't corrupting for me because I'm using the webrender compositor and a nightly build. Menus aren't working though, but that's another bug! ;-)

[K4rakara]

I'm also encountering this on an AMD RX570.

Like what Xyene experienced, it also disappears when a layer surface is present.

However, I've only had it happen with xwayland apps. Specifically discord and (rarely)alacritty (I have alacritty set to run under xwayland due to a minuscule bug).

Firefox doesn't have this issue for me though; but I'm using MOZ_ENABLE_WAYLAND=1, so that might be why.

[emersion]

Can you share Sway debug logs?

It seems like I'm only able to reproduce when modifiers aren't supported. With modifiers enabled the bug doesn't appear.

[emersion]

This amdgpu patch fixes it for me: https://lore.kernel.org/amd-gfx/20210920103133.3573-1-contact@emersion.fr/T/#u