I haven't reproduced it so far in 16.10 developer preview. I agree with Merlijn in comment #19 that when it did happen previously, it was frequently related to some display crash or display refresh whgen system was starting.
I haven't reproduced it so far in 16.10 developer preview. I agree with Merlijn in comment #19 that when it did happen previously, it was frequently related to some display crash or display refresh whgen system was starting.