[regression] Grid Plugin does not restore maximized windows correctly.

[Jjed]

After a terminal application is dragged to the top panel, it will not unmaximize to original proportions, but rather detach from the top panel without changing size.

To reproduce (both in currently released and trunk Unity):

 1. Open gnome-terminal
 2. Drag the terminal up to the panel to maximize
 3. Drag the terminal down to unmaximize (or click the unmaximize button). Observe the window maintains maximized proportions

Interestingly, if you switch focus to another application after step 2, the terminal *will* restore correctly.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity 6.12.0daily13.02.19.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Mar 1 15:24:28 2013
InstallationDate: Installed on 2012-10-30 (122 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to raring on 2013-02-21 (8 days ago)

[Brandon Schaefer (brandontschaefer)]

Thank you for reporting this bug. I can confirm this on compiz 0.9.9. Seems to be something to due with the Grid plugin.

[Sami Jaktholm (sjakthol)]

Although this bug happens often with grid plugin, it's not the root cause of this issue (there was a bug in grid that has kept this problem hidden in the past). This bug can be reproduced with only core loaded by maximizing and restoring terminal window using key bindings.

When the window is unmaximized, gnome-terminal decides to recalculate its size (it reacts to focus in/out events, and when a keybinding or restore button is pressed, compiz steals the focus). For some reason it's using the maximized window geometry as a base of the process.

Also check out bug 1102024 (it's practically the same bug as this one but with different way to trigger it).

[Brandon Schaefer (brandontschaefer)]

Interesting, I hadn't dug very far into the problem. Lets mark this a duplicate as that bug you mentioned, and add this other way to reproduce it on the other bug. Thanks for the comment :).