Bug 485145

Summary: Visual glitches when maximizing a window with always-visible floating panel
Product: [Plasma] plasmashell Reporter: fanzhuyifan
Component: PanelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: minor CC: bienalle999, justintwayland, kde, kdetester, leohearts10, miren_radia, nate, niccolo.venerandi, niccolo, relayvk, sighunter, subhasutra
Priority: NOR Keywords: regression
Version: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=488893
Latest Commit: Version Fixed In: 6.2.0
Sentry Crash Report:
Attachments: buggy behavior

Description fanzhuyifan 2024-04-06 18:38:05 UTC
SUMMARY


STEPS TO REPRODUCE
1. Create always visible floating panel
2. double click the titlebar of a window to maximize it

OBSERVED RESULT
The side that maximizes against the floating panel first go past the panel, and then move back to the correct location (see screencast)

EXPECTED RESULT
The side that maximizes against the floating panel should directly go to its final position.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0

ADDITIONAL INFORMATION
Comment 1 fanzhuyifan 2024-04-06 18:43:59 UTC
Created attachment 168228 [details]
buggy behavior

can't reproduce on 6.0.3, so this is probably a recent regression.
Comment 2 Niccolò Venerandi 2024-04-07 15:40:21 UTC
Does this still happen if you remove all panels except one? Or even if you remove the left one?
Comment 3 fanzhuyifan 2024-04-07 16:03:36 UTC
(In reply to Niccolò Venerandi from comment #2)
> Does this still happen if you remove all panels except one? Or even if you
> remove the left one?

Yes to both questions.
Comment 4 cwo 2024-06-20 17:49:27 UTC
*** Bug 488793 has been marked as a duplicate of this bug. ***
Comment 5 Miren Radia 2024-06-21 08:55:40 UTC
I can also reproduce a similar glitch when I change desktop to one where there is a [vertically] maximised window.

My software versions are
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-1260P
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Framework
Product Name: Laptop (12th Gen Intel Core)
System Version: A6
Comment 6 Justin Wayland 2024-06-22 20:41:25 UTC
On 6.0.5, can't reproduce this either, if that helps.
Comment 7 subhasutra 2024-06-22 21:42:22 UTC
I can reproduce this as well, started with plasma 6.1 update. Firefox sometimes gets stuck in this back and forth animation and some part of webpage ends up being behind the panel. However minimising the app fixes it.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.9.5.arch1-1
Graphics Platform: Wayland
Comment 8 Nate Graham 2024-06-26 19:56:11 UTC
Can reproduce.
Comment 9 cwo 2024-06-30 20:26:52 UTC
*** Bug 489506 has been marked as a duplicate of this bug. ***
Comment 10 ainz 2024-07-01 08:28:54 UTC
Can reproduce this as well. More noticeable when panel position is set to the top.

Software versions:
Operating System: Arch Linux 
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.6.36-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Comment 11 Nate Graham 2024-07-18 15:46:46 UTC
This appears to be fixed in current git master, perhaps with the floating panel refactor patches.
Comment 12 Nate Graham 2024-07-27 03:37:26 UTC
*** Bug 490548 has been marked as a duplicate of this bug. ***