https://bugs.kde.org/show_bug.cgi?id=507291
Bug ID: 507291
Summary: Custom Panel / Bar Overlap
Classification: Plasma
Product: kwin
Version First 6.4.0
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: xwayland
Assignee: kwin-bugs-n...@kde.org
Reporter: ins...@no.capfr.fr
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
