I have been having the same problem for weeks on KDE 6.6 beta on Arch. I just found out that changing the setting for the screen for color precision from efficiency to precision makes the artifacts disappear. I am waiting for the bug to be fixed in the driver so I can switch back and save power but in the meantime it makes it more usable
1 Like
I think I have the same issue? But since the most recent (?) amd-firmware update I can’t get my external Displays to show anything when not connected to the dedicated gpu port in the back…
Hello all.
I had the same glitch since several days now. I run ArchLinux on a Framework 16 with an AMD Ryzen 7 7840HS and a Radeon 780M, with Plasma 6.6.2 over Wayland and the Kernel is 6.18.16-1-lts.
I apply the kernel parameter as suggested earlier, without success.
I remark that glitch on the Konsole window, when I move or resize it. I pay attention, and see the glitch matches sometimes what’s behind the Konsole window (there were KCalc behind, and I’m pretty sure that I saw the numeric buttons in the glitch)
Anyway… I remember that my KDE desktop freezed abruptly without being able to do something else than a reboot with “CTRL+ALT+DEL”. The culprit was DDCUTIL at that time. Downgrading the version make the success. Plus, the DDCUTIL following patch removed a modification and, since then, I did not have any desktop freeze… But I ask myself if this is not a DDCUTIL issue again.
I created an issue to try and fix the driver bug causing this. If you have the same issue consider upvoting it.
Want to add on to this thread that I upgraded from Fedora KDE 42 to Fedora KDE 43 this past week, on my Framework 16 7940HS/780M with 7700S GPU, and I started experiencing these same graphical glitches. I can confirm that setting amdgpu.dcdebugmask=0x410 has eliminated the artifacts on my system. Interestingly if I switched to an X11 Plasma session, I didn’t notice the artifacts (this is before setting the debug flag). I also noticed that while many times the artifacts crossed the whole screen, sometimes they would remain isolated to a specific window, to the ghost of a dismissed context (right-click) window, or even just to a text cursor in one case. The artifacts also didn’t appear on either the built-in or external monitor when connected to an external monitor, both via the back port and an expansion module port.