desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #06283
[Bug 224845] Re: With dual monitors (TwinView), maximized windows start up in wrong screen
is this bug still being looked at in Natty Narwhal? I get this same
behavior with Ubuntu 11.04/Gnome 2.32.1/NVIDIA driver 280.13/Compiz
0.9.4.0 on a 7600 GT AGP card.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/224845
Title:
With dual monitors (TwinView), maximized windows start up in wrong
screen
Status in The Metacity Window Manager:
Fix Released
Status in “metacity” package in Ubuntu:
Fix Released
Bug description:
I am using two displays, after I added these relevant changes to the
default xorg.conf (and enabled the restricted nvidia driver):
Option "TwinView"
Option "MetaModes" "1280x1024 1280x1024"
Option "TwinViewOrientation" "LeftOf"
If I close gedit (or firefox or thunderbird, ...) while it's in a
maximized state, the next time it will start in my left virtual screen
every time. No matter if I start it from a gnome panel on either
monitor, or via Alt-F2, or from a console.
The main window does actually get created on the virtual screen where
the mouse pointer is. But after 1/10 of a second it invariably gets
moved to the left screen.
If I leave the main window unmaximized before closing it, the next
time I start gedit , it will start on the correct screen.
Perhaps related to this: I've initially seen this on Firefox, so I
tried the mozilla.org 3.0b5 linux binary and got the same behaivour.
But if I try with Firefox 2.0.0.14 from mozilla.org, the window gets
created on the correct screen when starting maximized. Unfortunately
as soon as I click anywhere on the window, it jumps to the left
screen.
Tested with (fresh ubuntu 8.04 install):
- firefox 3.0~b5+nobinonly-0ubuntu3
- gedit 2.22.1-0ubuntu1
- metacity 1:2.22.0-0ubuntu4
- nvidia-glx-new 169.12+2.6.24.12-16.34
- xserver-xorg 1:7.3+10ubuntu10
To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/224845/+subscriptions