3:06 a.m.
Hi there,
at first let me express how much I am impressed by Inkscape.
Since the 0.48 version (text upper/lower case at last!) Inkscape has
grown into a viable alternative to Illustrator here. Thanks to the devs
and all the others who contributed!
Maybe someone can help me with my Latex formula issue?
Using 0.48 with Linux Mint 9 (Isadora) when I render a formula, an info
box pops up saying that the called script has given additional
information to inkscape, no error had been thrown and the result might
be unusable (sorry, dialogue in german so no literal citation), the
message inside the box is "Segmentation fault". The formula gets
rendered correctly though.
It's not a big thing, but having to click away that dialogue each time I
render a formula in order to see the result is a bit annoying. I can
find no log files, strace shows nothing of interest. So maybe someone
can help me find the cause of the message or a way to suppress it.
TIA!
Cheerz,
Lars
9:41 a.m.
On 6/5/11 12:06, Lars Behrens wrote:
Using 0.48 with Linux Mint 9 (Isadora) when I render a formula, an
info
box pops up saying that the called script has given additional
information to inkscape, no error had been thrown and the result might
be unusable (sorry, dialogue in german so no literal citation), the
message inside the box is "Segmentation fault". The formula gets
rendered correctly though.
It's not a big thing, but having to click away that dialogue each time I
render a formula in order to see the result is a bit annoying. I can
find no log files, strace shows nothing of interest. So maybe someone
can help me find the cause of the message or a way to suppress it.
Most likely the segfault comes from pstoedit (do a google search,
reported for several linux distros).
What happens if you call pstoedit by itself (even without any arguments)
on the command line?
Which version of pstoedit do you have installed?
~suv
1:09 a.m.
Am 06.05.2011 18:41, schrieb ~suv:
Most likely the segfault comes from pstoedit (do a google search,
reported for several linux distros).
What happens if you call pstoedit by itself (even without any arguments)
on the command line?
Which version of pstoedit do you have installed?
Yes, you are right. The segmentation fault message
("Speicherzugriffsfehler" in German) is printed out everytime I call
pstoedit.
***********************************************************************
pstoedit: version 3.50 / DLL interface 108 (build Jan 25 2010 - release
build - g++ 4.4.3) : Copyright (C) 1993 - 2009 Wolfgang Glunz
No output format specified (-f option) and format could not be deduced
from suffix of output file since no output file name was given
Usage: "pstoedit -f format inputfile outputfile" or run "pstoedit
-help"
to get a complete list available options.
Speicherzugriffsfehler
***********************************************************************
So it is a matter of suppressing the output of pstoedit or, as a
workaround, tell the extension script to ignore it.
Thank you for your hint.
Cheerz,
Lars
1:58 a.m.
Am 10.05.2011 10:09, schrieb Lars Behrens:
or, as a
workaround, tell the extension script to ignore it.
For those who need it:
Replacing
if not line.startswith('pstoedit: version'):
with
if not line.startswith(('pstoedit: version', 'Speicherzugriffsfehler',
'Segmentation fault')):
(or whatever segfault may be called the actual language) in eqtexsvg.py
helps here, as a verrry dirty workaround.
Cheerz,
Lars
4592
days inactive
4596
days old
inkscape-user@lists.inkscape.org
3 comments
2 participants
participants (2)
-
Lars Behrens -
~suv