Bug#817195: Same observation

2016-03-22 Thread Benj. Mako Hill
I am suffering from the same bug. > 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 v

Bug#817195: Same observation

2016-03-22 Thread Michael Hanke
Hi, On Sat, Mar 19, 2016 at 01:38:51PM +0100, Julien Cristau wrote: > On Tue, Mar 15, 2016 at 15:34:18 +0100, Michael Hanke wrote: > > If this package is responsible, the most recent upgrade in my system > > happened on 2016-03-11, upgrading from 2.99.917-2 to > > 2.99.917+git20160218-1. > > > Yo

Bug#817195: Same observation

2016-03-19 Thread Julien Cristau
On Tue, Mar 15, 2016 at 15:34:18 +0100, Michael Hanke wrote: > Hi, > > I seem to observe the exact same behavior on a machine with a different > chipset > > 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor > Graphics Controller (rev 09) > > and using a Display Port c

Bug#817195: Same observation

2016-03-15 Thread Michael Hanke
Hi, I seem to observe the exact same behavior on a machine with a different chipset 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) and using a Display Port connection. Gnome shell in use also. It doesn't depend on the particular DP devic