SUMMARY KWin Wayland reports "Invalid framebuffer status: 'GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT'", causing graphical issues. STEPS TO REPRODUCE Boot the system and log into KDE Plasma with Wayland. I use the system normally, especially with graphically intensive applications. OBSERVED RESULT Multiple log entries showing "kwin_scene_opengl: Invalid framebuffer status: 'GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT'". EXPECTED RESULT No such errors should occur, and the desktop environment should function without graphical issues. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nobara 42 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kel Version: 6.14.6-200.nobara.fc42.x86_64 Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT ADDITIONAL INFORMATION OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.1.0
Please attach the full kwin log (journalctl --user-unit plasma-kwin_wayland --boot 0) after you see the graphical issues. Also, what do those issues look like?
Created attachment 181629 [details] kwin_log
(In reply to Zamundaaa from comment #1) > Please attach the full kwin log (journalctl --user-unit plasma-kwin_wayland > --boot 0) after you see the graphical issues. > > Also, what do those issues look like? Thank you for your reply. I have attached the full KWin log as requested, generated using the command journalctl --user-unit plasma-kwin_wayland --boot 0 after observing the graphical issues. The file is named kwin_log.txt. Regarding the graphical issues, they typically manifest as flickering or black screens when interacting with certain applications, especially those that are graphically intensive (e.g., games or 3D rendering software). Sometimes, the entire desktop environment becomes unresponsive for a few seconds, and I notice visual artifacts like distorted windows or missing UI elements. These issues occur intermittently, often after a period of normal usage, and are more frequent when running applications that rely heavily on OpenGL. Let me know if you need any additional information or if there’s anything else I can do to help diagnose this issue.
Alright, this is the same as bug 485884 then *** This bug has been marked as a duplicate of bug 485884 ***