Comment 8 for bug 755599

I confirm this is due to the patch introduced to fix bug 750753 .
The fix wasn't tested with the metacity compositor running, which displays this issue.
Regular metacity doesn't have this problem, so as a workaround you can disable the compositor until a proper fix is released.