Comment # 2 on bug 54174 from 
With Mesa 10.1 this problem still remains.

You are receiving this mail because: