Bug 217131

Summary: dual screen: maximized windows extend "under" the plasma panel under certain conditions
Product: [Plasma] kwin Reporter: Thomas Meixner <tom.meixner>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: screenshot of plasma panel covering maximized window.

Description Thomas Meixner 2009-12-02 22:58:36 UTC 
Version:            (using KDE 4.3.4)
Compiler:           arch binary 64Bit stock build (whole KDE suite)
OS:                Linux
Installed from:    Archlinux Packages

If the plasma panel in a dual screen setup is placed between 2 stacked up monitors, maximized windows will extend  below the plasma panel. This happens if the plasma panel is either at the bottom of monitor 2 or at the top of  monitor 1. (refer to drawing). Windows will only stop at the plasma panel border if the panel is either at the very top or very bottom of the stacked setup.

Monitor 1 is my main laptop monitor. The plasma panel usually is on the top. Monitor 2 extends to the top without any plasma panel since it's not always available.

 ______________
|              |
|  Monitor 2   |
|              |
|##############|

|##############|
|              |
|   Monitor 1  |
|              |
|______________|

# marks the position of the plasma panel where maximizing windows doesn't work as expected

Additional info: 
plasma panel: "Always visible" selected
In System Settings -> Display -> Multiple Monitors all options are selected
Comment 1 Thomas Meixner 2009-12-02 23:05:24 UTC 
Created attachment 38775 [details]
screenshot of plasma panel covering maximized window.

Image shows in the above described scenario monitor 1 (1440x900) and a maximized window going below the panel. Monitor 2 (1920x1080) is located above Monitor 1.
Comment 2 lucas 2009-12-03 02:26:56 UTC 

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