I assume that you are both using the latest DRI driver from dri.sourceforge.net right? Have they been informed of the bug? It sounds like something they'd want to fix. --brendan