Small bug causing problems with upcomming versions of cairo. Patch found in comment 4 of linked bug report: https://bugs.freedesktop.org/show_bug.cgi?id=54657 Reproducible: Always
Has this been reported upstream? If not, please do so. I would expect the patch (or something similar) to be applied and a new release made available within days.
It has been reported upstream, but this project is not really in active development anymore. Updates do happen occasionally, but they are getting further and futher apart. Feel free to park this report for a while and see if it happens.
(In reply to comment #2) > It has been reported upstream, but this project is not really in active > development anymore. Updates do happen occasionally, but they are getting > further and futher apart. I strongly disagree. He's made six releases this year, that's more than most other projects. He's always responded quickly to fix bugs. It may not be as active as it once was, but I see no evidence that it's even close to becoming dormant. I'll wait till the end of the week. If no upstream response is forthcoming, then we will apply this ourselves.
I think we can give upstream even more time, like 1 or 2 weeks... Btw what is this "upcoming version of cairo" that is going to break qtcurve? When is it expected to be released?
(In reply to comment #4) > Btw what is this "upcoming version of cairo" that is going to break qtcurve? > When is it expected to be released? cairo 1.12.4 and 1.12.6 have been released, I guess those are the new versions you were referring to...
Please include that patch as cairo 1.12.6 has hit the tree and the missing call is quite annoying... thx
+*gtk-engines-qtcurve-1.8.15-r1 (14 Nov 2012) + + 14 Nov 2012; Ben de Groot <yngwin@gentoo.org> + +files/gtk-engines-qtcurve-1.8.15-cairo.patch, + +gtk-engines-qtcurve-1.8.15-r1.ebuild: + Add patch to fix cairo rendering problem, bug #436742
