Comment 152 for bug 1010794

(In reply to comment #126)
> > The *bug* is neither in libcairo nor in any gfx driver, the bug *is* in xorg
> > (see headers of this bugreport and the whole bugreport posts itself). And a side note, some
> > foss devs may even be a little bit biased there, as shocking as that might
> > sound. ;)
>
>
> Well I'm used to that including proving people they are wrong even if they feel
> they know everuthing beter than others ;-) And BTW, people confirm the bad
> intercation between cairo and impress
You did not prove anything. It still stands the bug seems to be in xorg and not in any gfx driver or libcairo, for now until proven otherwise.
For the bad interaction between libcairo 1.12 and loimpress... I don't see how it is worse from what I experience on one box here with terminals, iceweasel, icedove, irc-client. And at least I read the analysis "Pauli" made in bug 49118 as a confirmation for the current assumption that xorg is at fault and that it may well be the same bug. On top of that in the Debian BTS both bugs (rather a dozen of bugs) are merged, confirming that it may well be the same bug too.

(In reply to comment #128)
> Did NOT fix he openoffice problem even for radeon driver as
> you can notice in one of the comment
Then there may be another issue apart from the up to now assumed broken EXA-pixmap-thingy in xorg. Or the workaround-fix in radeon does not work for that kind of usage of libcairo for loimpress. In general quite confusing. Lets hold back our semi-educated assumptions and allegations and let the devs do their work. This issue affects almost every user with recent libcairo on desktops, so the pressure is high enough for the devs already.

regards
Michael