Bug 310246 - maximized windows go below panel only when using two screens although "Always visible" is specified
Summary: maximized windows go below panel only when using two screens although "Always...
Status: RESOLVED DUPLICATE of bug 167852
Alias: None
Product: plasma4
Classification: Unmaintained
Component: panel (show other bugs)
Version: 4.9.3
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-17 14:48 UTC by Barade
Modified: 2013-06-07 13:23 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barade 2012-11-17 14:48:27 UTC
On my system I have two screens enabled, one LVDS and one HDMI (which is the primary). Both screens have one panel at the bottom of their display. For both panels I have specified "Always visible" but windows still go below them.
When I disable the HDMI and make the LVDS the primary output it works as expected on the LVDS only. When I enable the HDMI again and make it the primary output it still works on the LVDS but not on the HDMI.
btw. when I enable the HDMI again the size of the background image of the LVDS is too large although it's specified as "Scaled, keep proportions".
The HDMI has a resolution of 1920x1200, the LVDS has 1366x768.
The HDMI has a folder view layout, the LVDS a default desktop one.
After disabling the HDMI output and enabling it again, I cannot open the panel settings in LVDS anymore. It is being closed immediately and switched into my browser window where I am writing this text. I can open it again.
I think all this and the resolution bug might occur because of changing the primary output which leads to moving one layout to another screen.

Reproducible: Always
Comment 1 Barade 2013-03-24 20:23:06 UTC
still present in KDE 4.10.1
windows go below the panel on my HDMI screen but not on the LVDS although "Always visible" is configured on both.
Comment 2 Martin Flöser 2013-06-07 13:23:18 UTC

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