Created attachment 169953 [details] Example with Minecraft running on Vulkan thanks to the vulkanmod (should work properly) SUMMARY Apps open in random screens instead of the main (and focused) one, and they flicker a lot while focused. STEPS TO REPRODUCE 1. launch your favorite Vulkan app with Wayland native mode 2. set it in fullscreen. 3. done. OBSERVED RESULT The apps open on wrong (random) screens, and flicker while in fullscreen. Sometimes they don't have an issue, sometimes they do. It's random... Hardly trackable because of lack of ways to get logs. EXPECTED RESULT The apps should run normally, without flickering. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void-Linux 6.9.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION - I can't find a way to get logs. - The issue doesn't seem to happen with my Void-Linux laptop, that runs the exact same config. - Dmesg prints nothing - the vulkan loader debug mode (VK_LOADER_DEBUG=all) prints nothing as well - Vulkan validation layers print nothing as well. I try my luck here, after trying on the Void-Linux github repo, then vulkan-loader repo.
What GPU are you using?
(In reply to Zamundaaa from comment #1) > What GPU are you using? Hello, thank you for your answer. My main configuration (which has this issue) runs with: CPU: R7 7800X3D RAM: 32Gb GPU: RX 7900 XTX Driver: Mesa 24.0.7
Okay. If you put KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and reboot, does the issue go away?
(In reply to Zamundaaa from comment #3) > Okay. If you put > KWIN_DRM_NO_DIRECT_SCANOUT=1 > into /etc/environment and reboot, does the issue go away? I'm not sure, but it seems like it works... What does this do ?
It disables an optimization that sometimes drivers don't handle correctly; if disabling it fixes the problem, then it's a driver bug. Please report this at https://gitlab.freedesktop.org/drm/amd/-/issues (once the site is up again, it doesn't work right now)
(In reply to Zamundaaa from comment #3) > Okay. If you put > KWIN_DRM_NO_DIRECT_SCANOUT=1 > into /etc/environment and reboot, does the issue go away? Apparently it was already reported, or at least, something similar was, i added my comment to try and help... I think we can close this thread now. Link: https://gitlab.freedesktop.org/drm/amd/-/issues/3402#note_2438198