SUMMARY I have two monitors, a primary 1440p 155Hz one and a secondary 1080p 75Hz monitor. When I have windows maximized on each, and then try to drag the window that's maximized on my secondary, the window on my primary immediately starts to display visual glitches and artifacting of some sort. Clicking on it resolves it. I've attached a video demonstration of the bug. STEPS TO REPRODUCE 1. Have a window maximized on each of the monitors 2. Drag the window that's maximized on the secondary monitor so it stops being maximized. OBSERVED RESULT Visual glitches start appearing on the main monitor. EXPECTED RESULT Nothing to happen with the window on the main monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Edition KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Kernel version: 6.10.4-200.fc40.x86_64 CPU: AMD Ryzen 5 5600 GPU: AMD Radeon RX 6600 Mesa version: 24.1.5
Created attachment 172707 [details] Demonstration of the glitching What happens when I drag my secondary monitor's window.
I can reproduce this, but not consistently. A workaround I have found is holding the shift button before releasing the window instead of maximising. You need to split the screen in at least two ways (horizontal/vertical) for that feature to work. I experience it in both chromium and firefox, but the former has it much worse. Monitor 1: 2560x1440@144hz 100% scaling Monitor 2: 3840x2160@60hz 150% scaling (left of monitor 1, 90 degrees tilted) Kernel: 6.10.6-arch1-1 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Mesa version: 24.1.6 CPU: AMD Ryzen 9 7950X3D GPU: AMD Radeon 7900 XTX
Yeah, I can also reproduce it with both a Brave and Firefox window. Happens almost consistently in my case, unless I have some window opened in the foreground as well. In that case, sometimes it does not glitch out.
Today it happened in a worse format than before, this time with OnlyOffice on the primary monitor. Moving any kind of window on the secondary monitor causes it. I added an attachment with this one.
Created attachment 173197 [details] Another instance
Are there any specific logs I can provide that might give some insight?
Does this still happen if you put KWIN_USE_BUFFER_AGE=0 into /etc/environment and reboot?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to Zamundaaa from comment #7) > Does this still happen if you put KWIN_USE_BUFFER_AGE=0 into > /etc/environment and reboot? This visual glitch still occurs when setting that variable to 0 and rebooting. I've also tried KWIN_DRM_NO_DIRECT_SCANOUT=1 which did not solve it either.
Created attachment 173913 [details] Showcase of the bug with KWIN_USE_BUFFER_AGE=0.
I managed to figure out that, at least on my end, the issue is completely resolved if I set my bottom floating panel to dodge window. Any other setting causes the windows to have these glitches.
(In reply to Adi Efendic from comment #11) > I managed to figure out that, at least on my end, the issue is completely > resolved if I set my bottom floating panel to dodge window. Any other > setting causes the windows to have these glitches. I can confirm! It does take a reboot for that workaround. There's just a tiny visual glitch left when clicking on 'Restore Down' on a maximized window, but nothing major as in the video I sent. It also disappears very quickly.
Having only 1 panel also fixes the problem. After removing all other panels you still need to reboot the machine.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
hmm, this wasn't supposed to be closed, was it? It's still happening for you, right?
If it does still happen, one more thing you could test: Does disabling the maximize effect change anything?