@Kazade, it's interesting that you saw this against xorg-edgers. For future reference, we provide xorg-edgers for testing purposes, so it is a good idea if you report bugs you find there, so we have a chance at dealing with them (or even skip doing the update) before the bugs get into the release. (I know reporting bugs can be a pain but I did go through mesa and xorg-edgers bug reports with a fine toothed comb before doing this update, so it would have definitely been of benefit in this case.)
Fwiw, I am planning on updating us to the -ati git snapshot such as the one in xorg-edgers currently. It would be helpful if you guys could confirm if this bug still occurs when running with that git snapshot. I'm guessing it will, but if you can confirm it, then I can get that bug reported upstream (and maybe try chasing down a patch, although time is short) before moving Karmic to this new -ati.
@Kazade, it's interesting that you saw this against xorg-edgers. For future reference, we provide xorg-edgers for testing purposes, so it is a good idea if you report bugs you find there, so we have a chance at dealing with them (or even skip doing the update) before the bugs get into the release. (I know reporting bugs can be a pain but I did go through mesa and xorg-edgers bug reports with a fine toothed comb before doing this update, so it would have definitely been of benefit in this case.)
Fwiw, I am planning on updating us to the -ati git snapshot such as the one in xorg-edgers currently. It would be helpful if you guys could confirm if this bug still occurs when running with that git snapshot. I'm guessing it will, but if you can confirm it, then I can get that bug reported upstream (and maybe try chasing down a patch, although time is short) before moving Karmic to this new -ati.