Bug 356412 - Windows are maximized under panel
Summary: Windows are maximized under panel
Status: RESOLVED DUPLICATE of bug 94470
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.4.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-09 08:21 UTC by Vit Pelcak
Modified: 2016-01-19 14:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
screenshot (90.04 KB, image/png)
2015-12-09 08:21 UTC, Vit Pelcak 		Details
output of panels xprop (59.00 KB, text/plain)
2016-01-19 14:37 UTC, abulak 		Details
output of xrandr -q (2.46 KB, text/plain)
2016-01-19 14:38 UTC, abulak 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Vit Pelcak 2015-12-09 08:21:25 UTC 
When I maximize window, it is behind the panel.

I have set panel to be always on top and never hide. Yet, maximized windows are behind it.
It is rather annoying as I have to resize windows manually to fit or have part of the window hidden.

See screenshot in attachment.

Reproducible: Always
Comment 1 Vit Pelcak 2015-12-09 08:21:52 UTC 
Created attachment 95944 [details]
screenshot
Comment 2 Thomas Lübking 2015-12-09 08:26:00 UTC 
please post the output of "xrandr -q" and "xprop" (for the latter click the panel after the cursor turned into a '+')
Comment 3 abulak 2016-01-19 14:37:13 UTC 
Something like this happens for me also, but:

a) only with second display attached, and
b) for the vertical panel on the edge connecting displays.

There is a similar bug filled (323230) but for much older version (4.11?)
This happens with kwin and kscreen from 5.5.3.
Comment 4 abulak 2016-01-19 14:37:52 UTC 
Created attachment 96735 [details]
output of panels xprop
Comment 5 abulak 2016-01-19 14:38:41 UTC 
Created attachment 96736 [details]
output of xrandr -q
Comment 6 Thomas Lübking 2016-01-19 14:56:36 UTC 

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