Comment 15 for bug 597987

Just a little extra info: from my searching around on the issue, it would appear that the remaining errors could well be down to incorrect usage of the Cairo API, rather than a bug per se. From the 1.9.10 release notes:

The last snapshot was picked up by the bleeding edge distributions and so the
    bug reports have to started to roll in. The most frequent of these are the
    introduction of rendering errors by applications that modify a surface
    without subsequently calling cairo_surface_mark_dirty(). Make sure the
    application developers are aware of increased reliance on strict use of the
    Cairo API before 1.10 is released!