Windows move to 0,0 on compiz restarts

Bug #858629 reported by Sam Spilsbury on 2011-09-25
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Compiz Core
Low
Sam Spilsbury
Unity
Fix Released
Low
Sam Spilsbury
compiz (Ubuntu)
Low
Sam Spilsbury
unity (Ubuntu)
Undecided
Unassigned

Bug Description

We don't invalidate the frame and wrapper window references when notifying the plugins that the window was unreparented, so some plugins may call through to configureXWindow which will attempt to move the client window into 0,0 inside the destroyed frame, but in fact the client is a child of the root window, so it will be moved to 0,0

Changed in compiz-core:
status: New → In Progress
Changed in unity:
status: New → In Progress
Changed in compiz (Ubuntu):
status: New → Incomplete
status: Incomplete → In Progress
Changed in compiz-core:
importance: Undecided → Low
Changed in unity:
importance: Undecided → Low
Changed in compiz-core:
assignee: nobody → Sam Spilsbury (smspillaz)
Changed in unity:
assignee: nobody → Sam Spilsbury (smspillaz)
Changed in compiz-core:
milestone: none → 0.9.5.96
Changed in compiz (Ubuntu):
assignee: nobody → Sam Spilsbury (smspillaz)
Changed in unity:
milestone: none → 4.18.0
Didier Roche (didrocks) on 2011-09-26
Changed in unity:
milestone: 4.18.0 → 4.20.0
David Barth (dbarth) on 2011-09-28
Changed in compiz (Ubuntu):
status: In Progress → Fix Committed
Changed in unity:
status: In Progress → Fix Committed
Changed in compiz-core:
status: In Progress → Fix Committed
Changed in compiz (Ubuntu):
importance: Undecided → Low
milestone: none → ubuntu-11.10
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package compiz - 1:0.9.6-0ubuntu1

---------------
compiz (1:0.9.6-0ubuntu1) oneiric; urgency=low

  * New upstream release 0.9.6:
   - Windows which are marked transients of docks should be treated like docks (LP: #860397)
   - Applications which create multiple windows that are transients of each other can be given invalid stack positions (LP: #858625)
   - race condition in configureXWindow causes unpredicatable window geometry changes (LP: #860304)
   - invisible window when a window is mapped but not yet drawn on by the process mapping it (LP: #860286)
   - resizing bugs with xterm (LP: #854725)
   - Cannot open a window that starts iconified (LP: #732997)
   - maximized windows fail to update their input extents when undecorated (LP: #853734)
   - Clicking on a tweet/message link sometimes does not work (LP: #790565)
   - crash on closing a window (LP: #856015)
   - Windows move to 0,0 on compiz restarts (LP: #858629)
   - windows that are decorated while resizing can cause incorrect resize results (LP: #860306)
   - remove transient window handling from unity-window-decorator (LP: #856096)
 -- Didier Roche <email address hidden> Wed, 28 Sep 2011 14:15:21 +0200

Changed in compiz (Ubuntu):
status: Fix Committed → Fix Released
Didier Roche (didrocks) on 2011-09-29
Changed in unity:
status: Fix Committed → Fix Released
Changed in compiz-core:
milestone: 0.9.5.96 → 0.9.7.0
Changed in compiz-core:
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers