Bug 482100

Summary: Maximize/minimize windows animations are very choppy because of the panel settings and Nvidia
Product: [Plasma] kwin Reporter: evgeniyharchenko.dev
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cagankota, jason, linux, nate, niccolo.venerandi, nicolas.fella, s_chriscollins, unlovable_fridge356
Priority: NOR Keywords: qt6
Version First Reported In: 6.0.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=482193
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Example

Description evgeniyharchenko.dev 2024-02-29 22:19:09 UTC
Created attachment 166225 [details]
Example

SUMMARY
Using Nvidia driver and X11 all actions with windows which triggers changing the appearance of the panel such as maximize/minimize are very laggy. There is no problem when panel is not floating and its opacity is not adaptive.

STEPS TO REPRODUCE
1. In Panel Settings set Opacity to Adaptive or switch on Floating.
2. Open any app.
3. Try to maximize/minimize it or make any other action which triggers changing the appearance of the panel. 

OBSERVED RESULT
Lags. Very choppy animation.

EXPECTED RESULT
Smooth animation.

SOFTWARE/OS VERSIONS
KDE Neon 6.0 (X11)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Nvidia driver: 545.29.06
Comment 1 Vlad Zahorodnii 2024-03-01 09:04:17 UTC
this bug report is not very actionable I'm afraid (mostly because nvidia)
Comment 2 Çağan 2024-03-01 21:06:40 UTC
I can reproduce this with NVIDIA 550 driver, on X11 too.
Comment 3 Jason Crevier 2024-03-02 00:59:53 UTC
(In reply to Çağan from comment #2)
> I can reproduce this with NVIDIA 550 driver, on X11 too.

Weighing in to say I can reproduce this on 545 and 550 (and Vulkan beta 535) on NixOS with X11.
Comment 4 boospy 2024-03-24 11:07:42 UTC
Yeah same here... workaround for me: Floatingpanel disabled.
Comment 5 Nate Graham 2024-03-27 16:42:20 UTC

*** This bug has been marked as a duplicate of bug 475468 ***