Bug 507291

Summary: Custom Panel / Bar Overlap
Product: [Plasma] kwin Reporter: insuna
Component: xwaylandAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: minor CC: kde
Priority: NOR    
Version First Reported In: 6.4.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description insuna 2025-07-21 06:07:29 UTC 
SUMMARY:
Until KDE 6.4.0 I could use my xwayland Polybar to add a custom bar on my secondary monitor. If I then maximized windows on that screen they would be bounded by the bar instead of the screen edge, as I would expect and desire. Additionally windows dragged towards the bar would collide with its edge until I applied "more pressure".
This no longer happens, the bars are now still there, and on the top stratum, but they no longer collide with other windows and instead just overlap with them.


STEPS TO REPRODUCE
1. Install Polybar
2. Configure and launch polybar
3. Observe that windows do not collide with the Polybar

OBSERVED RESULT
Windows dragged into the polybar overlap with polybar.

EXPECTED RESULT
Windows dragged to polybar should collide and require intention to be placed into an overlapping position.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Linux 6.15.3
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Not exactly critical, but very annoying when you're trying to use a terminal on the second screen and the line where you want to input commands is hidden by the bar, because the terminal was maximized.

My ideal solution would be a kwin rule that I could add that just grants a window collision, or goes back to how it was before and just automatically adds the bounding box.
Comment 1 David Edmundson 2025-07-21 09:42:22 UTC 
It is intended that we stop supporting the X features for making DE level integration, sorry.

Consider using waybar.
Comment 2 insuna 2025-07-21 10:25:16 UTC 
(In reply to David Edmundson from comment #1)
> It is intended that we stop supporting the X features for making DE level
> integration, sorry.
> 
> Consider using waybar.

Waybar does not support what I need. Either way, why is it not possible for kwin rules to restrict the screen space / create colliders / create a bounding box?
Comment 3 insuna 2025-08-30 07:06:05 UTC 
(In reply to David Edmundson from comment #1)
> It is intended that we stop supporting the X features for making DE level
> integration, sorry.
> 
> Consider using waybar.

Can you tell me in which commit this feature was broken so that I can revert it locally? Thank you