linux-traipu team mailing list archive

[Sam Spilsbury <smspillaz@xxxxxxxxx>]

** Changed in: unity
       Status: Confirmed => Fix Released

** Changed in: unity (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: chromium-browser (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/787277

Title:
  Undecorated windows have host decorations placed on them after
  maximize/unmaximize cycle

Status in Chromium Browser:
  Unknown
Status in Unity:
  Fix Released
Status in “chromium-browser” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  This problem affects VMware Unity (which uses undecorated host windows
  to render Virtual Machine guest windows as shown here:
  http://www.flickr.com/photos/chipx86/2384035553/), Google Chrome (as
  documented here: http://ubuntuforums.org/showthread.php?t=1742354 and
  according to the Chromium bug report here:
  http://code.google.com/p/chromium/issues/detail?id=80856), and other X
  applications who ask to not be decorated.

  This can be easily reproduced with Ubuntu 11.04, running Unity mode
  (I'm running 3d currently), with Google Chrome:

  1) Install Ubuntu 11.04, sign into Ubuntu Unity mode
  2) Install and start Google Chrome. By default this comes up undecorated, though it can be set in Google Chrome's preferences
  3) Maximize the Google Chrome window
  4) Unmaximize the Google Chrome window
  5) Observe that now Google Chrome is decorated, even though it was set to undecorated prior to the maximize/unmaximize cycle.

  This also happens with our VMware Unity windows. We use
  gtk_window_set_decorated(false), which I believe uses _MOTIF_WM_HINTS
  behind the scenes for all of our windows. Here's what xprop -spy shows
  when our window comes up:

  _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x0, 0x0, 0x0
  _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
  WM_NORMAL_HINTS(WM_SIZE_HINTS):
  		program specified location: 0, 0
  		program specified minimum size: 0 by 0
  		window gravity: NorthWest
  WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
  WM_CLASS(STRING) = "Notepad.VMwareUnityWindow", "Notepad"

  When the user maximizes the window in the guest, I see these property
  changes via xprop -spy:

  _NET_WM_ICON_GEOMETRY(CARDINAL) = 9, 777, 48, 48
  _NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ
  _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x0, 0x0, 0x0

  (note that we don't actually set _NET_WM_STATE_MAXIMIZED* on our
  window... that's set by Compiz). And this is what I see when the user
  unmaximizes the window:

  _NET_WM_STATE(ATOM) = 
  _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x1, 0x0, 0x0
  _NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_STICK, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
  _NET_FRAME_EXTENTS(CARDINAL) = 1, 1, 22, 1
  _COMPIZ_WINDOW_DECOR_INPUT_FRAME(WINDOW): window id # 0x540102f
  _COMPIZ_WINDOW_DECOR(INTEGER) = 20110130, 1, 33583828, 1, 1, 22, 1, 1, 1, 22, 1, 0, 0, 22, 1, 0, 0, 22, 1, 26, 0, 589925, -15, -32, -6, 0, 766, 32767, 0, 0, 524389, 751, -32, -6, 0, 32767, 32767, 766, 0, 590182, -6, -32, 17, 0, 23, 32767, 790, 0, 395413, -15, 0, 0, -222, 32767, 223, 1, 34, 264341, -15, 223, 0, -222, 32767, 32767, 224, 34, 395929, -15, -222, 0, 0, 32767, 222, 447, 34, 395430, 0, 0, 17, -222, 32767, 223, 1, 51, 264358, 0, 223, 17, -222, 32767, 32767, 224, 51, 395946, 0, -222, 17, 0, 32767, 222, 447, 51, 589993, -15, 0, -378, 21, 394, 32767, 0, 70, 524457, 379, 0, -378, 21, 32767, 32767, 394, 70, 590250, -378, 0, 17, 21, 395, 32767, 790, 70
  _COMPIZ_WM_WINDOW_BLUR_DECOR(INTEGER) = 4, 0, 5, 4, -22, 6, -4, -21, 5, 2, -21, 6, -2, -20, 5, 1, -20, 6, -1, -19, 5, 0, -19, 6, 0, -17, 5, -1, -17, 6, 1, 0, 9, -1, 0, 10, 1, 1, 5, -1, 0, 9, 0, 0, 6, 0, 0, 10, 1, 0

  So Ubuntu Unity seems to be changing _MOTIF_WM_HINTS on us and it
  shouldn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/787277/+subscriptions