Created attachment 138892 [details] Thats how it looks on my screen - screenshots looking normal by the way SUMMARY When using any vukan-application in full-screen mode there are only weird colored artifacts displayed. I noticed this behavior in the dolphin emulator and in retroarch even in the menu (which is good for testing purposes). When I am switching to the opengl backend or using windowed mode, everything is just working fine. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.21.90 from KDE unstable repository KDE Frameworks Version: 5.83.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Intel i915 driver mesa vulkan driver - vulkan-intel intel hd 620
Do visual artifacts persist if you disable compositing?
Is it even possible to disable compositing in a plasma wayland session? I just turned the compositor to xrender and to the open gl 2/3 backend and the result was the same every time
Oh, no, you can't disable compositing on Wayland. I thought that this bug report is about X11. This seems like a modifier related issue.
Git commit 19f92d731aca686b1365db9b032f5ca961f5be26 by Xaver Hugl. Committed on 08/06/2021 at 14:38. Pushed by zamundaaa into branch 'master'. platforms/drm: fix modifiers detection M +1 -1 src/plugins/platforms/drm/drm_gpu.cpp M +3 -0 src/plugins/platforms/drm/egl_gbm_backend.cpp https://invent.kde.org/plasma/kwin/commit/19f92d731aca686b1365db9b032f5ca961f5be26
Git commit 18c0525422a000247b5d487af77deb9428be0c0c by Xaver Hugl. Committed on 08/06/2021 at 15:54. Pushed by zamundaaa into branch 'Plasma/5.22'. platforms/drm: fix modifiers detection (cherry picked from commit 19f92d731aca686b1365db9b032f5ca961f5be26) M +1 -1 src/plugins/platforms/drm/drm_gpu.cpp M +3 -0 src/plugins/platforms/drm/egl_gbm_backend.cpp https://invent.kde.org/plasma/kwin/commit/18c0525422a000247b5d487af77deb9428be0c0c
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1083
Can you test if the commit fixes the issue?
I installed the newest version of kwin and the problem is solved now. Thank you :)
Do you mean latest git master or the newer merge request?
I meant in the git master.
Great!
*** Bug 438618 has been marked as a duplicate of this bug. ***