XWayland fullscreen corruption on Intel ANV
System information
- OS: Arch Linux
- GPU: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98]
- Kernel version: 5.12.10-arch1-1
- Mesa version: 21.1.2
- Xserver version (if applicable): 1.20.11
- Desktop manager and compositor: KDE Plasma 5.22.0 (Wayland)
- Wayland version: 1.19.0
- Wayland Protocols version: 1.21
- XWayland version: 21.1.1
Describe the issue
When running Sascha Willems's Vulkan examples in fullscreen using XCB, the application window will become corrupted. This issue will resolve itself if the X window is out-of-focus, but can reappear when back in focus. Taking a screenshot via Spectacle will also momentarily fix the problem (the screenshot will come out fine). Observing the application using OBS Studio also comes out fine (see screenshots).
I am not sure whether this is a Wayland bug or a Mesa bug, so I am filing it here for now.
Other observations:
- This will not occur if not running in fullscreen
- This will not occur if Wayland is used (
-DUSE_WAYLAND_WSI=ON
is specified in CMake) - I can reproduce this issue with games via Proton as well (Proton 6.3-4, using bundled DXVK)
- Wolfenstein II: The New Colossus - The corruption occurs during the intro sequence, and persists until I quit the game
- Warframe - Corruption occurs when setting the game to Borderless Fullscreen or Fullscreen
- I have not been able to reproduce this issue with any OpenGL applications, including:
- Full Screen mode of any Jetbrains IDE (e.g. IntelliJ IDEA)
- Google Chrome via XWayland
- glxgears in fullscreen
Screenshots/video files (if applicable)
gltfscenerendering
Expected (running with --vsync
):
gltfscenerendering
Actual (running with --vsync --fullscreen
):
gltfscenerendering
via OBS Studio 27.0.0 (running with --vsync --fullscreen
):
Any extra information would be greatly appreciated
I am not sure if this issue is related to #836 (closed), so I am creating a new issue.
This issue occurred when I switched from using an AMD dGPU (RX 6800) to the iGPU. I am reasonably certain that I have pruned all packages and commented all configurations related to AMDGPU.
This issue cannot be reproduced using RADV on my AMD laptop (GPU: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1))