After using this for a few days, I've determined that enabling HWCursor
does not actually fix the problem. At least not long term. It actually
seems as though HWCursor has been switched off (although it is still
enabled in my xorg.conf) I'm not exactly sure how HWCursor works,
but... First when
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/showthrea
