Summary: | _NET_WM_STRUT and _NET_WM_STRUT_PARTIAL aren't set to the panel size | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Will Price <will.price94> |
Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kde, thomas.luebking |
Priority: | NOR | ||
Version: | 5.4.0 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Will Price
2015-09-03 20:22:44 UTC
Is this the same as: https://bugs.kde.org/show_bug.cgi?id=349191 After additional experimentation, yes, this is a duplicate of #349191. Sorry for not finding that, I did search before posting, but I was only searching for the atom strings and not struts hence I didn't pick that bug report up. *** This bug has been marked as a duplicate of bug 349191 *** I'm not sure this is a dupe. The report strikingly leaks a problem description, ;-) but > I'm running two monitors, a 1920x1200 screen displayed above a 1280x768 screen sounds incredibly like bug #299247 ? Sorry, it is indeed a duplicate since I'm not running KWin but XMonad instead. Steps to reproduce: 1. Set up two monitors, monitor 1 should be above monitor 2 2. Set monitor 2 as the primary screen so that the plasma panel appears on it 3. use `xprop` to check the _NET_WM_STRUT_PARTIAL atom, it should consist of all zeroes. The problem in the other bug is not exactly kwin. The main question is "where is your panel" - if it's on top (ie. "between the screens") this is bug #299247 If not, it may still be something different. Bug #349191 is rather specific and should only have any impact if xwininfo -root | grep geometry differs from xrandr -q | grep current (the values, not the formatting ;-) Sorry for dismissing the other bug so quickly. The output doesn't differ between the two command outputs, and after reading through bug #299247 I agree with you that this report is a duplicate of that. *** This bug has been marked as a duplicate of bug 299247 *** Sorry for dismissing the other bug so quickly. The output doesn't differ between the two command outputs, and after reading through bug #299247 I agree with you that this report is a duplicate of that. |