That's the switcher frame being left behind bug. This will be fixed in
the next natty update
On Tue, Jun 7, 2011 at 7:07 AM, Paul van Genderen
<email address hidden> wrote:
> Either this hasn't been fixed yet or there's another issue which hasn't
> been properly triaged yet. It occurs rather frequently, even inside the
> text box where I'm writing this comment right now. It's as if there's a
> hidden-but-always-on-top U-shaped window, but it could be a box as well.
> I wanted to make a screencast but I could only click the istanbul icon
> once. I think it's still recording. Anyway, I used a camera phone to
> record the attached video but I couldn't see it myself because of
> #327082. FGLRX is enabled.
>
> ** Attachment added: "bug.webm"
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/723014/+attachment/2157922/+files/bug.webm
>
> --
> You received this bug notification because you are a member of Canonical
> Desktop Experience Team, which is a bug assignee.
> 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
>
> Status in Unity:
> Fix Released
> Status in “compiz” package in Ubuntu:
> Fix Released
> Status in “unity” package in Ubuntu:
> Fix Released
> Status in “compiz” source package in Natty:
> Fix Released
> Status in “unity” source package in Natty:
> Fix Released
>
> Bug description:
> Binary package hint: compiz
>
> Currently we aren't tracking windows that haven't been mapped in the
> case that they are override redirect, however sometimes these windows
> can be destroyed by the time CreateNotify arrives and we might get
> Configure requests to try and stack windows relative to them however
> since they are not in our internal window lists this will fail and
> cause weird things to happen. For example
>
> - Invisible windows (windows being managed the wrong way around)
> - On suspend resume, gnome-screensaver creates a few windows then destroys them right afterwards, this causes weirdness when it tries to stack relative to those windows and fails.
>
That's the switcher frame being left behind bug. This will be fixed in
the next natty update
On Tue, Jun 7, 2011 at 7:07 AM, Paul van Genderen but-always- on-top U-shaped window, but it could be a box as well. /bugs.launchpad .net/ubuntu/ +source/ compiz/ +bug/723014/ +attachment/ 2157922/ +files/ bug.webm /bugs.launchpad .net/bugs/ 723014
<email address hidden> wrote:
> Either this hasn't been fixed yet or there's another issue which hasn't
> been properly triaged yet. It occurs rather frequently, even inside the
> text box where I'm writing this comment right now. It's as if there's a
> hidden-
> I wanted to make a screencast but I could only click the istanbul icon
> once. I think it's still recording. Anyway, I used a camera phone to
> record the attached video but I couldn't see it myself because of
> #327082. FGLRX is enabled.
>
> ** Attachment added: "bug.webm"
> https:/
>
> --
> You received this bug notification because you are a member of Canonical
> Desktop Experience Team, which is a bug assignee.
> https:/
>
> Title:
> New window tracking system breaks in the case where windows try to
> restack relative to destroyed windows that were never mapped
>
> Status in Unity:
> Fix Released
> Status in “compiz” package in Ubuntu:
> Fix Released
> Status in “unity” package in Ubuntu:
> Fix Released
> Status in “compiz” source package in Natty:
> Fix Released
> Status in “unity” source package in Natty:
> Fix Released
>
> Bug description:
> Binary package hint: compiz
>
> Currently we aren't tracking windows that haven't been mapped in the
> case that they are override redirect, however sometimes these windows
> can be destroyed by the time CreateNotify arrives and we might get
> Configure requests to try and stack windows relative to them however
> since they are not in our internal window lists this will fail and
> cause weird things to happen. For example
>
> - Invisible windows (windows being managed the wrong way around)
> - On suspend resume, gnome-screensaver creates a few windows then destroys them right afterwards, this causes weirdness when it tries to stack relative to those windows and fails.
>
--
Sam Spilsbury