This bug affects me too, and I may have found a workaround. The report gave a hint that if they chmod'd /usr/bin/unity-window-decorator, things seem to work again, but without Compiz. That made me investigate CCSM a little bit.
If you open CCSM and go to the "Window Decoration" plugin under "Effects", you can change the path of the window decorator that Compiz uses. In my case, I changed the "Command" to /usr/bin/gtk-window-decorator instead of /usr/bin/compiz-decorator (presumably an alias for unity-window-decorator), and on first blush the problem seems to be gone.
This bug affects me too, and I may have found a workaround. The report gave a hint that if they chmod'd /usr/bin/ unity-window- decorator, things seem to work again, but without Compiz. That made me investigate CCSM a little bit.
If you open CCSM and go to the "Window Decoration" plugin under "Effects", you can change the path of the window decorator that Compiz uses. In my case, I changed the "Command" to /usr/bin/ gtk-window- decorator instead of /usr/bin/ compiz- decorator (presumably an alias for unity-window- decorator) , and on first blush the problem seems to be gone.