← Back to team overview

compiz team mailing list archive

[Bug 723014] Re: New window tracking system breaks in the case where windows try to restack relative to destroyed windows that were never mapped

 

Running a fairly well-updated version of the Natty beta, and I'm having
this issue. At first I thought it was Chrome being weird, but it's
definitely certain regions of the screen that don't respond to any mouse
clicks.  Seems like there may have been a regression?

Linux emperornattyx64-U33Jc 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Compiz 0.9.4.0
unity 3.8.6

Unrelatedly, "compiz -v" cores, saying that -v is an unknown option,
despite the insistence of the man page that it's a valid shorthand for
--version.  I might file a separate bug report for this if I can't find
another record of it.

I'm happy to provide debug support today if anyone has the time to
suggest test cases, etc.  Also, if any additional information about my
system would be helpful, let me know.

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/723014

Title:
  New window tracking system breaks in the case where windows try to
  restack relative to destroyed windows that were never mapped



References