After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 512742 - Metacity places all new maximised top-level windows on left-most monitor
Metacity places all new maximised top-level windows on left-most monitor
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
trunk
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2008-01-29 09:07 UTC by Chris Lord
Modified: 2014-06-08 14:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Chris Lord 2008-01-29 09:07:46 UTC
Please describe the problem:
I have a xinerama with two monitors. Both are 1280x1024, my primary monitor on the right and a second head directly to the left. When I start a new application that starts maximised, with my mouse cursor on the primary monitor, it momentarily appears on the primary monitor, then 'warps' to the second monitor.

Steps to reproduce:
1. Setup monitors as described above
2. Start totem and maximise it on the primary (right) monitor
3. Close totem
4. Re-open totem with the mouse-cursor on the primary monitor

Actual results:
Totem appears on the primary/right monitor, briefly, then suddenly moves to the left-most monitor.

Expected results:
I would expect totem to stay on the monitor with the mouse cursor, or at least not just randomly switch monitor

Does this happen every time?
Yes, and happens with other applications too (Evolution, Firefox..)

Other information:
Maybe this has something to do with how the application restores its state, as it doesn't seem to affect devhelp. Nevertheless, I'm sure this didn't use to happen.
Comment 1 Chris Lord 2008-08-06 07:12:07 UTC
This may be a duplicate of #504692, but I'm not sure.
Comment 2 Alberts Muktupāvels 2014-06-08 14:13:56 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.