https://bugs.kde.org/show_bug.cgi?id=461824
--- Comment #10 from Zamundaaa <xaver.h...@gmail.com> --- (In reply to Minik from comment #4) > Created attachment 153765 [details] > Diagnostic_logs > > Here are my diagnostic logs (dmesg, journalctl, drm_info for desktop and > fullscreen) compressed in .tar.gz I see no relevant warnings in dmesg or journalctl. From the drm_info contents though I can see that you do get direct scanout with fullscreen, and the game provides a XRGB8888 buffer, while KWin uses the ARGB2101010 format when it does compositing. It's possible that switching between these formats triggers some bug in the kernel. To check if it's relevant you can put KWIN_DRM_PREFER_COLOR_DEPTH=24 into /etc/environment, reboot, and see if the problem can still be caused. No matter if that works or not, it might be useful to get more detailed logging for the broken setup from the kernel, which you can do by following the instructions at https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues. Keep in mind that it's very verbose, so the time you record dmesg should be as short as possible. (In reply to raffarti from comment #8) > dmesg is flooded by > `[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer > with error -22` > nothing else to see there... Sounds exactly like https://gitlab.freedesktop.org/drm/amd/-/issues/2075. Please add a comment to that, to show you're affected as well, and to hopefully make someone at AMD attempt to fix the problem. Putting KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment should be a usable workaround for you. -- You are receiving this mail because: You are watching all bug changes.
