https://bugs.kde.org/show_bug.cgi?id=407784
--- Comment #20 from razangriff-ra...@tutanota.com --- Created attachment 120929 --> https://bugs.kde.org/attachment.cgi?id=120929&action=edit Screenshot 1 Sadly I cannot afford to run other drivers. My current work needs the nvidia binary drivers, things don't render well with the free ones. Something else which is interesting is that thumbnails are detecting changes. (I have "keep thumbnails" as always. Although, from what you said, shouldn't that feature not work at all with compositing disabled?) Look at the included screenshot, it's a bit hard to tell if you don't use Godot, but I managed to get the Godot window in the back frozen when launching the project. The game had an error, and it should be showing the debugger screen below (ignore the screen in front, since the project crashed it's all weird and "hall of mirrors"-y, that's normal, I didn't want to move it out of the way to not disturb the crime scene). If you look at the thumbnail from the task manager, it's showing the current state of the window, with an error in red, while the window itself is entirely frozen even when it's changing actively (and I think it even sets an alert state). So, the big question is, if the culprit is not kwin, what other component of KDE that has changed from 5.15.5 to 5.16.0 could be causing this. Let me reiterate that rolling back does fix it. Anyway, things I know: -Enabling and disabling "keep window thumbnails". No change. -Enabling and disabling compositing in all 3 backends. No change. -Disabling vsync with flipping enabled/disabled in nvidia-settings. No change. -Reverting to 5.15.5. The issue doesn't happen again. -Downgrading nvidia drivers. No change. -Upgrading nvidia drivers. No change. -Reverting to the nvidia drivers I had to begin with. No change. -Disabling hardware acceleration in Discord and Chromium. They aren't affected anymore, but perform a bit worse. This is not viable for Atom, it's too slow to use otherwise. Downright impossible to do with Godot or Blender as it's always accelerated. -Upgrading plasma but not kwin. The issue doesn't happen. -Killing kwin makes windows update again. The problem doesn't happen with no window manager. -Switching desktops, minimizing and restoring the window, resizing the window, switching compositor state will unfreeze the windows, but they will freeze again eventually. -Ubuntu default desktop cannot reproduce the issue (hardly a solution, I consider it unusable and can't waste time tinkering with it). -Tried installing other X11 window managers like icewm or fvwm. Issue doesn't happen either. -Windows exclusively freeze when a new accelerated window is created. If no windows are created at all, the issue won't trigger ever. -Switching back and forth between windows, even quickly, does not seem to trigger it either. Only window creation as far as I can tell. Additional notes: -I use a single screen setup, very basic. -The only non-default plasmoid I have is Latte-Dock. -No exotic or unusual hardware, just keyboard, mouse and a wacom tablet, none give issues in KDE or other desktops/apps. -KDE install is pretty much default. The only unmanaged KDE tool is Krusader which I compile from git. And Krita from their PPA (which I installed after creating this issue). No other additional changes to it. -No changes to kernel or any fancy patches. No unusual video hacks or anything either other than the nvidia-settings slider set to max performance. -No unusual cpu or video load, video glitching or anything strange when windows freeze, they just remain static even if windows move in front of them (unlike the execution aborted Godot window in the attachment which has a "hall of mirrors" thing to it) -No settings at user level that could affect things. .profile just contains various program options, no preload hacks or anything. -Most "exotic" app in the whole system is fcitx for language support. Shouldn't be a factor, but just in case. -- You are receiving this mail because: You are watching all bug changes.
