Window size wrong when maximizing window after plugging in larger second monitor

[Steve Magoun]

I minimized a full-screen browser window on my laptop, plugged and turned on an external monitor, and restored the window. The resulting window is not sized correctly - the tabs are not visible because they are either off the top of the scrren or behind the panel. The left edge of the window is hidden behind the launcher (which I have set to display permanently - no autohide).

To reproduce:
1`) Open a fullscreen browser window. I am using FF
2) Minmize the window
3) Enable an external monitor (1280x1024 in my case, vs my laptop's internal screen of 1440x900). I am using NVIDIA's 'twinview' feature to extend the desktop to the second screen.
4) Click on the browser icon in the launcher to restore the window

Expected results:
The browser window is restored on the laptop's internal screen (my primary display). The browser window is sized as it previously was.

Actual results:
The browser window is restored on the laptop's internal screen but the tabs at the top of the screen are cut off and the left edge of the window is hidden behind the launcher. The browser window contents look correct (and tabs are included) in the alt-tab switcher and the view of all windows you get from Super-W.

I do not know whether this only happens if you enable an external monitor, and I don't know whether the size of the external monitor relative to the primary/laptop display matters.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 290.10 Wed Nov 16 17:39:29 PST 2011
 GCC version: gcc version 4.6.2 (Ubuntu/Linaro 4.6.2-14ubuntu1)
.tmp.unity.support.test.0:

ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,imgjpeg,decor,snap,imgpng,place,dbus,session,mousepoll,regex,commands,vpswitch,wall,neg,move,gnomecompat,resize,imgsvg,resizeinfo,text,animation,workarounds,fade,expo,scale,ezoom,unityshell,scaleaddon]
CompositorRunning: compiz
Date: Fri Feb 17 10:26:38 2012
DistUpgraded: Log time: 2012-01-26 16:01:56.788410
DistroCodename: precise
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00a0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
MachineType: Apple Inc. MacBookPro3,1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-16-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2012-02-13 (3 days ago)
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 03/05/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP31.88Z.0070.B07.0803051658
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4238BC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4238BC8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
dmi.product.name: MacBookPro3,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Steve Magoun (smagoun)]

Further investigation shows that all maximized windows are broken in this way. Quitting + relaunching apps doesn't help.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[linuxgeoff (linuxgeoff)]

similar problem and additional observation:

1) I've consistently had the exact same problem as described

2) In addition, I found a new mode today:

i. I switched from a single mode to dual monitor mode and thereafer my maximized windows on the larger remote screen were incorrect: the top of the window was about half way up the screen, and the right side was about 20 px outside the screen; the left and bottom aligned correctly. All applications I tried behaved this way. I'd never seen this before. Maximizing on the smaller primary display worked fine throughout

ii. logging out, restarting, disabling/reenabling 2nd display, resizing 2nd display all made no difference.

iii. because of teh above and on a whim, I tried moving the relative position of the screens because I observed that I had set the bottom of the larger remote screen slightly above the bottom of the laptop screen. As soon as I repositioned it so that the y location of smaller screen was within the Y envelope of the larger screen, maximizing a window on the larger screen started behaving correctly

iv. so the above is hopefully a hint as to what's causing the bug - and a potential workaround for those in the same situation. hope it all makes sense