Comment 3 for bug 151621

I have also experienced this bug. From what I gather, it only seems to happens when using a compositing window manager with the proprietary nvidia driver. It also seems that you can work around it by enabling HWCursor as described in the following thread. http://www.nvnews.net/vbulletin/showthread.php?t=90738