Inkscape 0.92.0 now available on MacPorts

David Rowe drowe at roden.myzen.co.uk
Sat Jan 7 19:17:21 CET 2017


On 07/01/2017 18:31, Murray Eisenberg wrote:
> I have latest (2..7.11) XQuartz installed under macOS Sierra 
> (10.12.2). I installed inkscape+quartz and insckape-app. When I either 
> run inkscape from Terminal command line or from inkscape.app created 
> by the latter, I see the XQiartz icon repeatedly appear and bounce in 
> my Dock and then disappear. But I never see an Inkscape window.
>
> How to fix?
>
I am getting something similar.

I initially installed inkscape at 0.92.0 (default) which installs the x11 
variant - but it wouldn't start up, so I tried inkscape @0.92.0_0+quartz 
but that fails the same way
I am running from the command line, and the following diagnostic 
information is output to the terminal:
<<<<<<<<<<<<<<<<SNIP:

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can 
fix it.

(inkscape:93783): Gtk-WARNING **: ChannelsAction: missing action 
ChannelsAction

(inkscape:93783): Gtk-WARNING **: ThresholdAction: missing action 
ThresholdAction

(inkscape:93783): Gtk-WARNING **: OffsetAction: missing action OffsetAction

(inkscape:93783): Gtk-WARNING **: PaintbucketUnitsAction: missing action 
PaintbucketUnitsAction

(inkscape:93783): Gtk-WARNING **: AutoGapAction: missing action 
AutoGapAction

. . . . about 50 other similar messages - ending:


(inkscape:93783): Gtk-WARNING **: ConnectorLengthAction: missing action 
ConnectorLengthAction

(inkscape:93783): Gtk-WARNING **: ConnectorDirectedAction: missing 
action ConnectorDirectedAction

(inkscape:93783): Gtk-WARNING **: ConnectorOverlapAction: missing action 
ConnectorOverlapAction
Segmentation fault: 11

 >>>>>>>>>>>>>>>END SNIP

For the record, I am running on a MacBook Pro (Retina, Mid 2012), with 
macOS Sierra 10.12.2 (16C67) and Macports 2.3.5 and xCode Version 8.2.1 
(8C1002)

Is anyone else getting this error? Does anyone else have any ideas?

David Rowe



More information about the macports-users mailing list