Bug 504173

Summary: [WAYLAND] Gap between widget and taskbar (using two taskbar-panels)
Product: [Plasma] plasmashell Reporter: hosgomaster
Component: PanelAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, nate, niccolo.venerandi
Priority: NOR    
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.4.0
Sentry Crash Report:
Attachments: Desktop screenshot of the problem

Description hosgomaster 2025-05-13 19:26:15 UTC
Created attachment 181254 [details]
Desktop screenshot of the problem

SUMMARY
Using Wayland there is an unwanted gap between widgets and the taskbar if you have two separate taskbar-panels in the e.g. bottom-left and bottom-right corner.

STEPS TO REPRODUCE
1. Enter Edit mode
2. Add Default Panel
3. Set Panel Settings -> Width: Fit content, Alignment: Left, Visibility: Dodge Windows
4. Repeat Step 2 & 3 once more
5. set position of the second Panel to the same site as the first one
6. Add a widget (e.g. the Sticky Note widget) and try to move it to the edge of the taskbar

OBSERVED RESULT
The widget can't be moved to the wanted position and gets resized.
There's always a gap as if the second panel is actually located above the first one.

EXPECTED RESULT
The widget is freely moveable to the edge of the panel.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
This bug only occurs with Wayland. Changing the display protocol to X11 makes the widget behave normally.
If the widget is too small to get resized, it can sometimes be moved closer to the panel.
Comment 1 hosgomaster 2025-05-13 19:42:20 UTC
I don't see an option to edit the bug description, so here's an annex: At step 5 you also need to set Alignment: Right for the second Panel.
Comment 2 Nate Graham 2025-05-13 20:15:35 UTC
This is fixed in Plasma 6.4.
Comment 3 Nate Graham 2025-05-13 20:15:52 UTC

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