User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030325 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030325 there should be an option to use the system installed libart if it exists e.g. configure could have an option --with-system-libart. I checked out the configure script, and the comments indicate that there are some moz specific patches to libart and the internal libart can be disabled once the patches are merged upstream. Reproducible: Always Steps to Reproduce:

BTW, the current version of libart is 2.3.12 while the version included with mozilla is 2.3.7+. So it would be better to link to the system libart instead of the internal one.

Our changes have been submitted to the libart list but AFAIK haven't been merged, so the trunk svg code still needs the patched version of libart. Having said that, the current svg development branch (SVG_20020806_BRANCH) tracked bug bug#182533 works with standard libart. The branch will replace the trunk code in the near future

Current libart is 2.3.16. Is this problem solved ?

We have 2 files in our libart directory (art_vpath.c, art_vpath.h) that haven't been merged into libart. I'm investigating moving this code to layout/svg/, so that we can move forward on this bug.

(In reply to comment #4) > We have 2 files in our libart directory (art_vpath.c, art_vpath.h) that haven't > been merged into libart. I meant art_vpath_filters.{c,h}.

should this be set to wontfix as moz uses cairo now ?

Marking wontfix. We have no plans to continue development of the libart backend.