Bug 510526

Summary: Taskbar overlaps maximized windows instead of windows auto-adjusting
Product: [Plasma] kwin Reporter: acfboyu
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, mail, nate, niccolo.venerandi
Priority: NOR    
Version First Reported In: 6.4.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshot shows the issue

Description acfboyu 2025-10-12 13:23:05 UTC
SUMMARY
Taskbar/panel overlaps maximized windows in Plasma 6.4.5 Wayland session
It seems similar to Bug 476961, but occurs again in 6.4.5

STEPS TO REPRODUCE
1. Open any application 
2. Maximize the window using maximize button or shortcut
3. Observe window behavior relative to taskbar/panel

OBSERVED RESULT
Maximized windows extend underneath the taskbar/panel, causing window content to be partially obscured. The window does not automatically adjust its size to account for the panel's space.

EXPECTED RESULT
Maximized windows should detect the taskbar/panel presence and automatically resize to fit the available screen space excluding the panel area, preventing overlap.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.4.0
Qt Version: 6.8.2
Comment 1 Francis Herne 2025-10-12 17:26:54 UTC
I am experiencing this with the standard full-width panel after upgrading to 6.4.5.
Comment 2 Nate Graham 2025-10-13 19:14:41 UTC
I can't reproduce this issue with today's git master. Please attach a screen recording that shows it happening. Thanks!
Comment 3 acfboyu 2025-10-18 04:24:32 UTC
Created attachment 185877 [details]
screenshot shows the issue
Comment 4 Nate Graham 2025-10-20 16:01:37 UTC
Is your panel using the "Windows go below" visibility mode?
Comment 5 acfboyu 2025-10-24 11:25:11 UTC
(In reply to Nate Graham from comment #4)
> Is your panel using the "Windows go below" visibility mode?

No.
Comment 6 Nate Graham 2025-10-24 16:18:37 UTC
Thanks. Does the issue happen in a new clean user account on the same computer with no customization?
Comment 7 acfboyu 2025-11-04 13:09:15 UTC
(In reply to Nate Graham from comment #6)
> Thanks. Does the issue happen in a new clean user account on the same
> computer with no customization?

Sorry, I reverted to the older version and can't provide more information about the error. However, I think the issue should also occur on a clean machine, as I made almost no custom custom configurations.
Comment 8 Nate Graham 2025-11-04 14:34:49 UTC
If you're not in a position to reproduce the issue anymore, and none of us could either, then unfortunately the bug has become un-actionable. :(