Comment 10 for bug 759154

> Was this issue reported upstream?

I had searched the bug tracker of cairo before - without success (I'm not familiar with coding in C++ myself, nor with the cairo internals called by Inkscape's export routines, and possibly didn't use matching keywords for my searches).

> If so, can someone share a link to the Cairo bug report please.

If known to the bug team, it would have been added as upstream link to this report already.

> Is there any method of working around this issue in Inkscape?

The only thing that comes to mind is creating a slight imprecision for the coordinates of the end nodes so that they don't share the same x- or y- coordinate.

> Maybe Inkscape could shorten the last segment by
> a tiny amount if broken version of Cairo is detected?

It seems that none of the developers was affected by this problem yet - consider asking on the developers' mailing list about ideas for workarounds for cairo 1.10/1.11 (whether Inkscape should implement hard-coded workarounds, or lend a hand to report and fix the upstream issue).