Bug 352239 - _NET_WM_STRUT and _NET_WM_STRUT_PARTIAL aren't set to the panel size
Summary: _NET_WM_STRUT and _NET_WM_STRUT_PARTIAL aren't set to the panel size
Status: RESOLVED DUPLICATE of bug 299247
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.4.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-03 20:22 UTC by Will Price
Modified: 2015-09-04 20:02 UTC (History)
2 users (show)

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 Will Price 2015-09-03 20:22:44 UTC
_NET_WM_STRUT and _NET_WM_STRUT_PARTIAL don't adhere to the freedesktop specification:

> _NET_WM_STRUT

> _NET_WM_STRUT, left, right, top, bottom, CARDINAL[4]/32
> This property is equivalent to a _NET_WM_STRUT_PARTIAL property where all start values are 0 and all end values are the height or width of the logical screen. _NET_WM_STRUT_PARTIAL was introduced later than _NET_WM_STRUT, however, so clients MAY set this property in addition to _NET_WM_STRUT_PARTIAL to ensure backward compatibility with Window Managers supporting older versions of the Specification.
(http://standards.freedesktop.org/wm-spec/1.3/ar01s05.html)

I'm running two monitors, a 1920x1200 screen displayed above a 1280x768 screen, the latter being the primary display.


`xprop` ouptut:


_NET_WM_STRUT(CARDINAL) = 0, 0, 0, 0
_NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
_NET_WM_USER_TIME(CARDINAL) = 266919554
_NET_WM_DESKTOP(CARDINAL) = 4294967295
_KDE_SLIDE(_KDE_SLIDE) = 0xffffffff, 0x1
_KDE_NET_WM_SHADOW(CARDINAL) = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION) = 0x3f625923, 0xbdadb9fd, 0xbdadb9fd, 0x0, 0xbe921b55, 0x3f2f02b8, 0xbe921b55, 0x0, 0xbcebfe56, 0xbcebfe56, 0x3f70b06f, 0x0, 0x3f2a3d71, 0x3f2a3d70, 0x3f2a3d70, 0x3f800000
_KDE_NET_WM_BLUR_BEHIND_REGION(CARDINAL) = 
_NET_WM_ICON(CARDINAL) = 	Icon (16 x 16):
XdndAware(ATOM) = BITMAP
WM_NAME(STRING) = 
_NET_WM_NAME(UTF8_STRING) = "Plasma"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x4, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_DOCK
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x2a00045
WM_HINTS(WM_HINTS):
		Client accepts input or input focus: False
		Initial state is Normal State.
_NET_WM_PID(CARDINAL) = 20522
WM_CLASS(STRING) = "plasmashell", "plasmashell"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		user specified location: 170, 1080
		user specified size: 1366 by 30
		program specified minimum size: 1366 by 37
		program specified maximum size: 1366 by 37
		window gravity: Static


Reproducible: Always
Comment 1 David Edmundson 2015-09-04 05:55:51 UTC
Is this the same as: https://bugs.kde.org/show_bug.cgi?id=349191
Comment 2 Will Price 2015-09-04 09:50:30 UTC
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 ***
Comment 3 Thomas Lübking 2015-09-04 12:56:52 UTC
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 ?
Comment 4 Will Price 2015-09-04 19:17:04 UTC
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.
Comment 5 Thomas Lübking 2015-09-04 19:43:50 UTC
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 ;-)
Comment 6 Will Price 2015-09-04 20:02:33 UTC
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 ***
Comment 7 Will Price 2015-09-04 20:02:50 UTC
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.