Nobara 40, Plasma 6.1.1 Wayland, nvidia-driver 555.58.02, kernel 6.8.12-201.fsync.fc40.x86_64, Lenovo Legion Slim 5 gen 8 with 240Hz display
For the life of me, I can’t seem to find a solution. Please help
While maximising or minimising windows, the windows on other monitors seem to glitch in a really weird way. Chunks of previous versions of windows seem to glitch in front of the actual window in strange and distorted ways. It doesn’t matter if the window is native Wayland or Xwayland. Switching to x11 fixes this bug, but it introduces a whole bunch of other bugs that I don’t want to deal with.
I have two monitors and a built-in display, the monitors being two 1440p 60Hz monitors, the built-in display being 2560x1600 240Hz.
I have tried multiple tweaks already, suggested by both Reddit threads, the Nobara Discord server and a few other sources:
Disabling triple buffering in /etc/environment (helped mitigate other graphical glitches
Disabling Adaptive sync (no effect)
Use udev rules as shown by this person: Reddit - Dive into anything (made everything so much worse, immediately reverted)
Some smaller tweaks that are either really small or I don’t remember making
Here is a link to a video showing the glitches in action (no download required):
I believe I can reasonably say that my hardware (e.g. cables) aren’t directly causing any trouble, as I use different cables and connectors for both my monitors + my built-in display and the bugs happen on all of them (some people reported that the problems are only caused on DisplayPort displays and not HDMI).
Whilst I don’t know if I can help you, I can say I think I’m in the same boat so perhaps we can compare notes. I’ve got a video of the issue I’m having too and it looks similar to your issue but as I’ve only just registered here to reply to you I’m not able to post a link.
I’m on a Lenovo ThinkPad P1 G7. Output of inxi -G is as follows:
I see our Nvidia driver versions match, and you’re on Nobara 40 which is based on Fedora. I’m using Fedora 40. I’m on a slightly newer kernel: 6.10.4-200.
My external monitors are ASUS VG27AQL1A models, one is running at 144Hz and the other at 60Hz, connected via a ThinkPad workstation dock.
Let me know if you make any progress and I’ll do the same.
As suggested by a user in a Reddit comment on my post entitled “Glitches when maximising and restoring windows” within the /r/KDE sub-reddit:
it’s a bug that’s caused by the panel trying to get into the maximized view (non floating mode) while another windows is alredy maximized, any change to this fixes the animation glitch, you can set the panel to autohide/dodge or set it to non float by default.
So, I disabled the floating panel and so far haven’t seen the issue. Fingers are crossed.
I tried disabling floating panels, and it actually fixed the bug! (๑>ᴗ<๑)
However, I found that while restoring windows (especially when doing so with the mouse instead of the button), the window likes to get much larger than it should for a small moment before returning to its normal size.
I believe this whole bug is a combination of this bug with the floating panels bug. I also saw on your Reddit post that you might report the bug via Bugzilla. Please let me know if/when you will go ahead with it.
I’m not entirely sure of what you’re describing but I think I’m seeing that with LibreWolf especially, which I’ve got running under Xwayland (due to some problems with native Wayland usage where context menus and select boxes open in the wrong place). Restoring the window briefly shows part of the window on my second monitor. Are you able to share a video showing this issue in particular?
Here is a video of the problem I was describing: Proton Drive (system is fully updated at the time of recording)
It doesn’t matter if I’m using a native Wayland app or an Xwayland app, I get this bug always. Disabling wobbly windows does make this problem more negligible, however I am suspecting this whole bug is related to the issue I was talking about in the beginning.
AFAIK, I haven’t seen any bugs like these reported upstream. I believe one of us reporting this bug to https://bugs.kde.org would be a great idea. In the worst case scenario, they will tell us that someone else has made a report before us.