Strictly speaking, this isn't a bug in the intel driver.. its a DRI2 problem. the Xorg server might also be relevant (since that is where DRI(1) works around this problem), but I think the fix will eventually land in Mesa.
Strictly speaking, this isn't a bug in the intel driver.. its a DRI2 problem. the Xorg server might also be relevant (since that is where DRI(1) works around this problem), but I think the fix will eventually land in Mesa.