0.49 MAC OSX returns error when saving to .DXF forma

Bug #1264858 reported by Ron Koch on 2013-12-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned

Bug Description

When "SAVING AS" from Inkscape MAC version 0.49 to a .DXF file, the following error dialogue appears and the .DXF file is written with 0 length:

"INKSCAPE has received additional data from the script executed. The script did not return an error, but this may indicate the results will not be as expected.'

In the text box below the informational header, this verbiage is displayed:

" The fantastic lxml wrapper for libxml2 is required by inkex.py and therefore this extension. Please download and install the latest version from http://cheeseshop.python.org/pypi/lxml/, or install it through your package manager by a command like: sudo apt-get install python-lxml"

This is running on a MAC-PRO, 3.33 GHz 6-core Intel Xeon / 12 GB DDR3 ram/ 2 x ATI Radeon HD 5770 - 1024 mb
MAC OSX: 10.9.1 (13842) MAVERICKS

Thanks

Ron Koch (rkoch1) wrote :

Should the lxml wrapper have been included with the install program?

su_v (suv-lp) wrote :

Thank you for the report - this is a known issue with the currently available Inkscape package for Macs, on Lion and later versions of OS X (including OS X 10.9 Mavericks), as tracked in
- Bug #819209 “Extensions do not work with Mac OS X Lion”
  <https://bugs.launchpad.net/inkscape/+bug/819209>

Currently there are unfortunately no new packages available which include a known fix for this solution - please see also the apology to Mac users here:
<http://inkscape.org/en/news/2012/12/22/inkscape-community-announces-0484-release/>

Linking as duplicate to bug #819209. Comment #17 of that report has instructions how to apply a fix locally to Inkscape 0.48.2 for Mac OS X.

> Should the lxml wrapper have been included with the install program?

The app does actually contain all required python modules - the problem is that the available Inkscape package for Mac OS X is rather dated and at the time the package was created it was not possible to anticipate changes in future versions of OS X releases.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers