Comment 99 for bug 296167

Matrox G450, Ibex, Xinerama, dual-head, using mga module with same patch as Nelson (#292214)

Exact same problem.. move and click events register one screen to the right of where the pointer appears, but nothing responds to the events except for xev, even if you correct for the shift.

I'm also getting lots of these messages from X on stdout or stderr as I move the mouse around:

Badness: Expose event on a client frame which shouldn't be visible: 0x#######

I'm also using wmii, if that matters