Bug 683031 – Window positioning in overview wrong when using multihead

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 683031 - Window positioning in overview wrong when using multihead


Summary:	Window positioning in overview wrong when using multihead


Status:	RESOLVED INCOMPLETE

Product:	gnome-shell
Classification:	Core
Component:	general
Version:	3.5.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gnome-shell-maint
QA Contact:	gnome-shell-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-08-30 13:13 UTC by Cosimo Cecchi
Modified:	2013-06-20 00:10 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
screenshot (192.46 KB, image/jpeg) 2012-08-30 13:15 UTC, Cosimo Cecchi	Details

Description Cosimo Cecchi 2012-08-30 13:13:54 UTC

See attached screenshot; you can see that the position of Chrome windows on the right monitor looks centered relative to the primary monitor rather than the one it's in.

Comment 1 Cosimo Cecchi 2012-08-30 13:15:09 UTC

Created attachment 222936 [details]
screenshot

Comment 2 Jasper St. Pierre (not reading bugmail) 2013-01-23 18:22:09 UTC

Does this still happen on gnome-shell master?

Comment 3 Matthias Clasen 2013-02-13 19:03:39 UTC

Doesn't seem to happen on my system, in a quick test.

Cosimo ?

Comment 4 Cosimo Cecchi 2013-02-13 19:21:00 UTC

Don't have a dual display setup to test with here ATM. Will try to reproduce this tomorrow in the office.

Comment 5 Jasper St. Pierre (not reading bugmail) 2013-02-18 09:22:25 UTC

Any luck?

Comment 6 Matthias Clasen 2013-03-11 03:58:28 UTC

moving multihead bugs off the 3.8 blocker list

Comment 7 Florian Müllner 2013-06-17 10:54:59 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 8 Allan Day 2013-06-20 00:10:13 UTC

Just tested this and it seems fixed, fwiw.