Good-bad news!
I can reproduce this bug again today, after updating my vivid desktop for the first time in two weeks. Seems some kernel/Mesa change has made it re-appear. And the INTEL_DEBUG workaround no longer works. But --nbuffers=3 does.
Good-bad news!
I can reproduce this bug again today, after updating my vivid desktop for the first time in two weeks. Seems some kernel/Mesa change has made it re-appear. And the INTEL_DEBUG workaround no longer works. But --nbuffers=3 does.