Compiz doesn't handle synthetic unmap notifies correctly
Bug #741072 reported by
Sam Spilsbury
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
High
|
Sam Spilsbury | ||
compiz (Ubuntu) |
Fix Released
|
High
|
Sam Spilsbury | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
See ICCCM section 4.1.4
"For compatibility with obsolete clients, window managers should trigger the transition to the Withdrawn state on the real UnmapNotify rather than waiting for the synthetic one. They should also trigger the transition if they receive a synthetic UnmapNotify on a window for which they have not yet received a real UnmapNotify ."
We are not treating the synthetic UnmapNotify any differently to the real one, so in effect compiz thinks the window is being unmapped twice. This is causing problems like invisible windows left behind (frame input windows) when windows are widthdrawn.
Changed in unity: | |
status: | Fix Committed → Fix Released |
tags: | added: patch |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package compiz - 1:0.9.4git20110 322-0ubuntu3
--------------- 4git20110322- 0ubuntu3) natty; urgency=low
compiz (1:0.9.
* 90_git_ fix_new_ invisible_ windows. patch:
from git, fix a case with new invisible windows (LP: #741072)
-- Didier Roche <email address hidden> Wed, 23 Mar 2011 17:36:06 +0100