Large windows switch monitor when maximized

Bug #948151 reported by Paul Natsuo Kishimoto on 2012-03-06
36
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Compiz Core
High
Unassigned
Unity
Incomplete
High
Unassigned
compiz (Ubuntu)
High
Unassigned

Bug Description

This bug occurs on multi-monitor setups with irregular geometry. I have two monitors of different size, in different orientations.

To reproduce:
1. Open a window on Display 1. Maximize, then restore. Resize it so it is larger in one dimension than Display 2. (1.png)
2. Move the window so it is visible only on Display 2. (2.png)
3. Double-click the title bar, or click the maximize button.

Expected: window maximizes on Display 2, where it is visible (3.png)

Observed: window maximizes, but returns to Display 1 (4.png)

Similar behavior can be observed by trying to maximize, on Display 1, a window which is wider than Display 1. The window moves to the wider display (Display 2).

This behaviour is unintuitive and did not occur before upgrading from 11.10 to 12.04; it is a regression.

$ apt-cache policy unity
unity:
  Installed: 5.4.0-0ubuntu2
  Candidate: 5.4.0-0ubuntu2
  Version table:
 *** 5.4.0-0ubuntu2 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Paul Natsuo Kishimoto (khaeru) wrote :
Paul Natsuo Kishimoto (khaeru) wrote :
Paul Natsuo Kishimoto (khaeru) wrote :
Paul Natsuo Kishimoto (khaeru) wrote :
tags: added: multimonitor
Omer Akram (om26er) wrote :

Thanks for the bug report. Can you please make a video of the problem you are facing that would make it easy for us to see the issue.

Changed in compiz (Ubuntu):
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
affects: unity (Ubuntu) → compiz-core
Omer Akram (om26er) wrote :

from the duplicate reports it seems quite a few people are facing this issue.

Changed in compiz-core:
importance: Undecided → High
Changed in unity:
importance: Undecided → High
Changed in compiz (Ubuntu):
importance: Undecided → High
icb410 (ian-berke) wrote :

Here's a video of the behavior. Sometimes it actually does work properly. Usually this occurs after snapping the window to half the monitor and then resizing across the desktop (see ~1.5-2min), however I can't consistently reproduce it or sometimes get it to go back to the buggy behavior. Hope this helps. Sorry for the poor quality of the video (it was my first screencast and I scaled down to make it a smaller file size).
Ian

Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 776435, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

icb410 (ian-berke) wrote :

Is this really a duplicate of bug #776435? The windows aren't being maximized to the wrong workspace, but to the wrong monitor on the same workspace in a dual-monitor setup. You also don't need the window to be half on the other monitor as was reported for the workspace bug, but just slightly wider than the smaller monitor dimension. In fact, if you put the window on the smaller monitor and shift it so that half of it is in the bottom workspace and maximize, it goes to the bottom workspace AND to the wrong monitor. This bug also did not occur in Oneiric, while the workspace one did.

Dylan Justice (dsjstc) wrote :

A slight refinement of description: a window larger in any dimension than the current monitor always gets maximized to the largest/primary monitor. Behaviour is 100% consistent on my system, comprising two portrait monitors 1024x1280 flanking a landscape monitor of 1920x1200.

Definitely not a duplicate of #776435, for reasons stated by icb410.

Daniel van Vugt (vanvugt) wrote :

OK, make that bug 760240 instead. Please feel free to generalize that bug so that it covers your use case.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers