Ah, yes. That does appear to be the same. Sorry for the duplicate, I searched but didn't find anything. The X modesetting driver does indeed fix the problem. I just can't figure out why this bug isn't a much bigger deal with all sorts of reports, as it seems like such a common hardware/driver/desktop combination.