Comment 1 for bug 165240

This seems to be a result of using the proprietary nvidia driver, so I guess there's nothing we can do about it.

I switched to the nv driver yesterday, and (so far) this problem has not recurred.