Comment 7 for bug 845719

OK, I'll poke around with focus-follows-mouse for a bit and see what I
can come up with.

There's also a pending update which may fix other issues.

On Wed, Oct 5, 2011 at 3:27 PM, Nick Moffitt <email address hidden> wrote:
> It's a cumulative thing that seems to take a day of regular use to
> arise, but I have a horrible intuition that it may be related to sloppy
> mouse focus (actually "mouse" mouse focus per gnome-tweak-tool) and
> switching desktops with keybindings.  The behavior seems to start after
> I've flipped from one workspace to another with keybindings, perhaps
> moving onto a maximized window.
>
> I've also noticed that selected desktop nautilus icons remain grey
> unless I move to a workspace that has no other windows on it.
>
> I'll try logging out and reproducing soon.
>
> ** Attachment added: "stacking.png"
>   https://bugs.launchpad.net/compiz-core/+bug/845719/+attachment/2511590/+files/stacking.png
>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is the registrant for Compiz Core.
> https://bugs.launchpad.net/bugs/845719
>
> Title:
>  compiz and X can disagree on the stacking order
>
> Status in Compiz Core:
>  Fix Released
> Status in Unity:
>  Fix Released
> Status in “unity” package in Ubuntu:
>  Fix Released
>
> Bug description:
>  This is a meta-bug to track all of the stack sync issues
>
>   * It is possible for a window to issue a ConfigureRequest in between ConfigureRequests internally and when we update the stack causing the ConfigureRequest in between the temporarily updated stack to be processed and given an invalid position
>   * It is possible for synethetic ConfigureNotify events sent to core in order to update frame windows can cause the stacking order to become invalid
>   * It is possible for created windows to invalidate the stack
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/compiz-core/+bug/845719/+subscriptions
>

--
Sam Spilsbury