https://bugs.kde.org/show_bug.cgi?id=491688
Bug ID: 491688 Summary: Vulkan artifacts when running through XWayland on Kwin without a color profile set Classification: Plasma Product: kwin Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compatibility Assignee: kwin-bugs-n...@kde.org Reporter: ozonehe...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY any time I am running an app through xwayland that use Vulkan I get horrible artifacts at first I thought it was a dying GPU but setting a color profile or running Plasma and Kwin in X11 session makes the artifacts go away STEPS TO REPRODUCE 1. Download Furmark 2.3 for Linux from their website 2. have an AMD RX 7800 XT with 2 1440p FreeSync Premium displays connected 3. run the Furmark (VK) benchmark OBSERVED RESULT you will see graphical artifacts EXPECTED RESULT it should not artifact when displaying something SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.4-zen2-1-zen (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X3D 12-Core Processor Memory: 61.9 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT ADDITIONAL INFORMATION I also found this when running journalctl --boot --follow --no-tail Aug 13 17:23:42 Ozzy-Pro wireplumber[1603]: wp-event-dispatcher: <WpAsyncEventHook:0x5b73bfe2f190> failed: <WpSiStandardLink:0x5b73bfe7ba50> link failed: some node was destroyed before the link was created Aug 13 17:23:46 Ozzy-Pro kwin_wayland[1513]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 Aug 13 17:23:46 Ozzy-Pro kwin_wayland[1513]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1) Aug 13 17:23:46 Ozzy-Pro kwin_wayland[1513]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Aug 13 17:23:46 Ozzy-Pro kwin_wayland[1513]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name) Aug 13 17:23:46 Ozzy-Pro kwin_wayland[1513]: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer) -- You are receiving this mail because: You are watching all bug changes.