This bug precisely describes my situation as well. I've seen this behavior under both the recommended (default activated) nvidia proprietary driver, and after disabling all nvidia proprietary drivers (which I guess relies on the nouveau open source driver).
This bug precisely describes my situation as well. I've seen this behavior under both the recommended (default activated) nvidia proprietary driver, and after disabling all nvidia proprietary drivers (which I guess relies on the nouveau open source driver).