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 344541 - Not moving a maximized window to another screen (xinerama)
Not moving a maximized window to another screen (xinerama)
Status: RESOLVED DUPLICATE of bug 323820
Product: metacity
Classification: Other
Component: general
2.6.x
Other All
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-06-11 03:47 UTC by Stéphane Rosi
Modified: 2006-06-11 05:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Stéphane Rosi 2006-06-11 03:47:39 UTC
Please describe the problem:
I have two screen using xinerama. 
With metacity 2.6.12.3, I could directly move a maximized window from one screen to the other by keeping the mouse cursor in the title area (so that the window is not unmaximized, moved to the other screen and then remaximized by placing it at the top of the new screen).
But since 2.6.14.1, when I do so, the window remains stuck in the initial screen and gets continuously unmaximized/maximized.

Steps to reproduce:
1. Set up two screens one on the side of the other with xinerama
2. Open a window and maximize it on one screen
3. Click on the title area and drag it to the other screen by keeping the mouse cursor in the title area until it is in the next screen


Actual results:
The window remains in the first screen. It is continuously unmaximized/maximized as if it wanted to change screen, but it doesn't...

Expected results:
The window to move directly maximzed on the other screen, as it happened with 2.6.12.3.

Does this happen every time?
Yes.

Other information:
If I first unmaximize the window by moving the cursor away from the title area, I can then move it easily to the other screen. But this is not as convenient as the previous behaviour.
Comment 1 Elijah Newren 2006-06-11 05:32:00 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 323820 ***