Compiz places unmaximized Chrome windows under the top panel

Bug #776424 reported by Luke Plant
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Compiz
Won't Fix
Low
Unassigned
compiz (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: compiz

When running compiz under Ubuntu Natty, classic mode not Unity, unmaximized Google windows are incorrectly placed. They always appear aligned to the top of the screen. This places the title bar underneath the Gnome panel, hiding the window controls and making it difficult to move them.

This can happen in a number of ways:

 - Open Google Chrome maximized (by having closed it maximized), and unmaximize it
 - Open Google Chrome unmaximized (by having closed it unmaximized)
 - Any javascript that opens a new Chrome window.

I can see how this might work well under Unity, but that isn't a reason to break it when Unity is not running.

This worked correctly under Maverick, and if I run metacity the Google Chrome windows behave as expected, so I'm filing it as a compiz bug.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Compiz, in particular, is in heavy development and this bug may have been fixed in the development version of Ubuntu (12.04) if not on your current version. If you are able, it would be of great help if you could confirm if the bug still exists by testing a livecd (available at ubuntu.com). When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue. If you are unable to test the development version, please let us know if you are able to reproduce this issue on Ubuntu 11.10.

Thank you for your help and patience.

Changed in compiz (Ubuntu):
status: New → Incomplete
Changed in compiz-core:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Compiz Core because there has been no activity for 60 days.]

Changed in compiz-core:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Cruz Bishop (cruzjbishop) wrote :

This still occurs in Ubuntu 12.04.1, using both stable and "dev" releases of Chrome.

Changed in compiz (Ubuntu):
status: Expired → Confirmed
Changed in compiz-core:
status: Expired → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Confirmed. This happens to me on precise often. Though I think it's mostly when I'm running dev builds of compiz (0.9.8).

no longer affects: compiz-core
Changed in compiz:
status: New → Confirmed
importance: Undecided → Low
Changed in compiz (Ubuntu):
importance: Undecided → Low
Revision history for this message
Eleni Maria Stea (hikiko) wrote :

We decided to close some old bugs that don't affect the supported Ubuntu releases. If you still experience this problem in any of the supported releases, please feel free to re-open it and update the description. Thank you!

Changed in compiz:
status: Confirmed → Won't Fix
Changed in compiz (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.