Wrongly placed maximized window with cloned display
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Undecided
|
Unassigned | ||
compiz (Ubuntu) |
Fix Released
|
Medium
|
Travis Watkins | ||
Hardy |
Fix Released
|
Medium
|
Travis Watkins |
Bug Description
Binary package hint: compiz
I am using Gutsy Tribe 2 on an Intel-Graphics based Notebook, and have switched the default "i810" driver to "intel". This driver by default clones the workspace content on both external and internal display, which means that my internal display only shows a subset (1280 x 768) of the external display (1920 x 1200).
Now on to the bug: When I maximize a window, it is maximized to the smaller (internal) display rather than the whole workspace. This looks and feels very strange.
I have seen other variations of this bug. When gksu dims the display, a "free-floating" compiz shadow is drawn around the virtual bounds of the smaller display, although there is no window that this shadow could belong to. The process of dimming up and down reveals a rectangle in the size of the smaller display. I've also had occasions of window move stickyness to the bounds of the smaller display.
To cut a long story short: Although the workspace is extended to the larger display, the bounds of the smaller display still play a role, which I think it shouldn't. I haven't had such effects with metacity.
Changed in compiz: | |
importance: | Undecided → Low |
Changed in compiz: | |
importance: | Low → Medium |
status: | New → Confirmed |
Changed in compiz: | |
assignee: | nobody → compiz |
assignee: | compiz → ubuntu-desktop-effects |
Changed in compiz: | |
assignee: | ubuntu-desktop-effects → nobody |
Changed in compiz: | |
assignee: | nobody → amaranth |
Changed in linux: | |
status: | Incomplete → Invalid |
This issue is still present on Tribe 5.