[ehendrix]

I've been seeing this multiple times before, each time when mainly working on my monitor through DisplayLink. It was actually confirmed as an issue in 2.0 and it looks like there might still be an issue there with 2.1