Bug 261674 - Windows cover panels when having screen “above” it
Summary: Windows cover panels when having screen “above” it
Status: RESOLVED DUPLICATE of bug 319840
Alias: None
Product: plasma4
Classification: Unmaintained
Component: panel (show other bugs)
Version: 4.8.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-31 00:28 UTC by Kai Uwe Broulik
Modified: 2013-05-15 10:10 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2010-12-31 00:28:07 UTC 
Version:           unspecified (using KDE 4.5.90) 
OS:                Linux

I have another screen configured “above” my notebook screen and noticed that applications cover the panel at the top of the lower screen. Even when chaning the visibility settings and setting them back to always visible leaves windows cover the panel.

Reproducible: Didn't try
Comment 1 Kolia 2011-12-03 19:21:21 UTC 
Hi, are u still experience this problem in a more recent version of KDE (4.7.x)?
Comment 2 Myriam Schweingruber 2012-05-21 23:32:43 UTC 
Closing for lack of feedback. Please feel free to reopen this report if you can still reproduce this with KDE 4.8.3 or later.
Comment 3 Kai Uwe Broulik 2012-05-28 11:48:39 UTC 
Now it's vice versa in 4.8.3:
The panel always covers the window, ie. the window is maximized to the entire screen size and no panel space preserved
Comment 4 Artur O. 2013-05-15 10:04:12 UTC 
[Multimonitor Issue]
Same issue here on ArchLinux, KDE 4.10.3
Also see https://bugs.kde.org/show_bug.cgi?id=284422

Got from [Enrico] on IRC that having TOP Y Axis of the monitors aligned is a workarround and indeed it is for me. Though not a really good one since that makes my mouse to warp up when switching monitor because of the placement.
Comment 5 Anne-Marie Mahfouf 2013-05-15 10:10:28 UTC 

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