Comment 4 for bug 935912

The culprit is "DISPLAY=:0.1 xrandr -r 24".

It always happens after switching the refresh rate of the second screen using
xrandr.