Since anything above low.cfg is pretty much unplayable anyway, this bug shouldn't cause too much problems

But if the problem persists with xf86-video-intel 2.5 (which has been released about a week ago), someone should file a bug report... (it won't be me, since i don't feel like building the driver myself, esp. since i don't use the intel gpu for 3D stuff anyway)