What's supposed to be responsible for setting capture_before_unmap to true? Right now, it's simply set to true in metacity.schemas, which doesn't fit with how Bill is saying it's supposed to work.
I generally notice this problem when switching workspaces, although it doesn't happen in every such situation. The following is a reliable way to reproduce it for me. I have a grid of four horizontal by three vertical workspaces; I have C-A-1, C-A-2, ..., C-A-0 bound to switch to each of the first ten of those twelve workspaces, and C-A-Left, C-A-Right, C-A-Up, and C-A-Down bound to move around the workspace grid in the obvious way. At the moment, I have maximised terminals open in the first three workspaces (and others). If I start from workspace 1, press C-A-3 to switch to workspace 3, then hold down C-A and press Left twice to switch back through workspace 2 to workspace 1, I find that parts of the workspace switcher remain on screen even after releasing C-A. (Don't release C-A between the two Left presses, or this bug won't happen.) I've attached the resulting screen image. ** Attachment added: "corruption.png" https://bugs.launchpad.net/ubuntu/natty/+source/metacity/+bug/740387/+attachment/2024293/+files/corruption.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740387 Title: graphical corruption with multiple drivers and classic desktop -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
