I agree with asac, we should keep the patch for hardy, just because it's too late.
I'm concerned by the 2nd part of the message in http://cairographics.org/news/cairo-1.5.18/
"(Meanwhile, there appears to be a separate bug where some X
servers or specific X-server drivers will use random pixmap data
when asked to draw a repeating surface. The buggy_repeat
workaround would also avoid those problems, but we have not yet
characterized whether the new "version < 1.4" is a good
characterization of those problems or not.)"
I think ATI (fglrx) is one of those. I will test locally (as I used to have that issue).
I agree with asac, we should keep the patch for hardy, just because it's too late. cairographics. org/news/ cairo-1. 5.18/
I'm concerned by the 2nd part of the message in http://
"(Meanwhile, there appears to be a separate bug where some X ation of those problems or not.)"
servers or specific X-server drivers will use random pixmap data
when asked to draw a repeating surface. The buggy_repeat
workaround would also avoid those problems, but we have not yet
characterized whether the new "version < 1.4" is a good
characteriz
I think ATI (fglrx) is one of those. I will test locally (as I used to have that issue).