I am suffering from the same bug. <quote who="Julien Cristau" date="Sat, Mar 19, 2016 at 01:38:51PM +0100"> > Your best bet is probably to actually check if reverting to an older > version of the intel driver fixes the issue, and if it does, to file > this upstream per > https://01.org/linuxgraphics/documentation/development/how-report-bugs Switching back to earlier versions of the kernel did not fix this bug. I tried this kernel packages linux-image-4.2.0-1-amd64 (4.2.6-3), linux-image-4.3.0-1-amd64 (4.3.5-1) and linux-image-4.4.0-1-amd64 (4.4.6-1) and the bug was present in all three cases. I switched back to the version of xserver-xorg-video-intel (plus dependencies) in jessie and the bug went away. The bug is present in 2:2.99.917+git20160218-1 and 2:2.99.917+git20160307-2 but switching back to an earlier version of xserver-xorg-video-intel (I just moved all the way back to 2:2.21.15-2+b2, the version in Jessie) eliminates the bug. This bug is a little outside of my wheelhouse but I can reliably reproduce this and I'm happy to help debug and fix this. Regards, Mako PS: I agree with the assessment that #818384 is a dupe of this bug. -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto
Attachment:
signature.asc
Description: PGP signature