https://bugs.kde.org/show_bug.cgi?id=455771
--- Comment #7 from Zamundaaa <xaver.h...@gmail.com> --- (In reply to McCak from comment #5) > (In reply to Zamundaaa from comment #4) > > Where did you export them? kwin_wayland needs to get them. Easiest way to > > ensure that is to put them into /etc/environment and rebooting > > oh yeah turns out the testing was wrong on my end.. yeah after adding those > env var the problem seems gone..Do u know exactly what happen here? Sorry about missing your response. The issue is caused by KWin directly using buffers from the game to drive the display (direct scanout); the driver tells KWin that doing that will work and yet when actually trying to present an image it fails. I'll ask around if compositors are expected to handle this situation but I think this is something the driver has to prevent 100% of the time or things will get a lot more complicated for compositors. Either way, this is a driver bug, can you report it to https://gitlab.freedesktop.org/drm/amd/-/issues? The relevant things to mention are that atomic commits fail with direct scanout on the dedicated GPU, and the error message you found before (kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22). If you link the issue here I'll try to provide any additional information that could help -- You are receiving this mail because: You are watching all bug changes.
