Comment 4 for bug 1471084

On 2015-07-03 18:09 (+0200), Terry wrote:
> So the work around is to downgrade Cairo?

As user? No.

It cannot be done with the Inkscape application bundle on OS X anyways; and I would never recommend to an Inkscape user to touch (downgrade) a system library on Linux. The examples I attached earlier had been possible to produce because I have 2 different, completely independent build environments set up which I use for testing local Inkscape trunk builds.

> Or should I just go back to Inkscape 0.48.1 or .2 that still had the
> old Cairo?

Not really either (I would not recommend it - apart from likely encountering earlier bugs from old cairo versions, you also might come across other Inkscape bugs fixed in later releases).

OS X packages:
- Inkscape 0.48.2: bundles cairo 1.10.2 (doesn't run on Yosemite!)
- Inkscape 0.48.5: bundles cairo 1.12.16 (affected)
- Inkscape 0.91 (32bit, 64bit): bundles cairo 1.14.0 (affected)

Windows packages:
- 32bit installer (0.48.5, 0.91): bundles cairo 1.11.2
- 64bit installer (0.91): bundles cairo 1.14.2 (affected)

My recommendation to users experiencing this cairo bug:
Consider changing the structure of problematic drawings (as long as you don't need to produce output files for laser cutters or plotters): strokes can be outlined (converted to path), fills kept as separate paths; some of the strokes are so thin that they make no visual difference at 100% zoom level and can be removed entirely; etc.