** Changed in: inkscape (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732
Title:
inkscape crashed with SIGABRT in
** Changed in: inkscape
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732
Title:
inkscape crashed with SIGABRT in
Fixed in the trunk, revision 12861.
** Changed in: inkscape
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732
Title:
inkscape
** Branch linked: lp:inkscape
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732
Title:
inkscape crashed with SIGABRT in
__gnu_cxx::__verbose_terminate_handler()
Status in
From comment #19 In the Win32 devlibs, we have libxml2-2.7.8 and in
Debian stable 2.8, both working correctly. Referring to your comment
#14, it fails with 2.9.1.
Tested again on Windows XP with the experimental gtk3 devlibs (with
libxml2-2.9), and I confirm it fails with the first 3 test files
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: inkscape (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
Another (external) extension affected by this crash triggered by
description parameters with newlines only (used as visual spacer):
Original Extension:
- “Inkscape to OpenSCAD converter v5”
http://www.thingiverse.com/thing:25036
http://www.thingiverse.com/download:209973
Patch (e.g. to be
~suv is it possible that a different external library is triggering
this regression (glib, libxml2, …)?
Since we use xml to get the element's content (defaultval =
xml-firstChild()-content();), yes, it could be due to some changes in libxml2.
In the Win32 devlibs, we have libxml2-2.7.8 and in
Attached is a patch that tests empty strings (in that case the description
widget is removed).
Please test!
** Patch added: 1204732-EmptyDescription.patch
https://bugs.launchpad.net/inkscape/+bug/1204732/+attachment/3769445/+files/1204732-EmptyDescription.patch
--
You received this bug
Confirmed on Windows XP, Inkscape trunk revision 12473 with example 1
from comment #7 (examples 2 and 3 doesn't crash the application).
** Changed in: inkscape
Status: Confirmed = In Progress
** Changed in: inkscape
Milestone: None = 0.49
** Changed in: inkscape
Assignee:
The attachment 1204732-EmptyDescription.patch seems to be a patch. If
it isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
On 2013-08-12 14:11 +0200, JazzyNico wrote:
Confirmed on Windows XP, Inkscape trunk revision 12473 with example 1
from comment #7 (examples 2 and 3 doesn't crash the application).
Thanks for noticing - I failed to catch that this particular crash with
a completely empty description also affects
It seems like the suggested patch fixes the symptom, not the underlying
cause; I would have guessed that the description inx element would be
the correct place to include desired whitespace.
While we have removed the empty parameters in the Eggbot and Hershey Text
extensions that caused the
Inkscape crashes when passing a NULL parameter to gettext. The check
just make sure the value is not NULL and if it fails, doesn't create the
description widget. I don't know if gettext should check, but it doesn't
hurt to check in Inkscape directly.
~suvThe rendered result of the INX file with
Also tested on Debian stable (Crunchbang flavor): with gettext
0.18.1.1-9, extensions fail1a, fail2 and fail3 don't crash and render as
expected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
On 2013-08-12 20:37 +0200, JazzyNico wrote:
Also tested on Debian stable (Crunchbang flavor): with gettext
0.18.1.1-9, extensions fail1a, fail2 and fail3 don't crash and render as
expected.
Ubuntu 13.10 Saucy Salamander also has gettext 1.18.1.1 installed
according to
AFAICT the trigger on Inkscape's side is an empty 'description' parameter (see
attached demos):
param name=empty_desc_1 type=description xml:space=preserve/param
or:
param name=empty_desc_1 type=description xml:space=preserve /param
or:
param name=empty_desc_1 type=description
Related upstream issue for Hersey text:
- Issue 62 - eggbotcode - Hershey Text causes Inkscape Trunk to crash
http://code.google.com/p/eggbotcode/issues/detail?id=62
** Bug watch added: code.google.com/p/eggbotcode/issues #62
http://code.google.com/p/eggbotcode/issues/detail?id=62
--
You
@Windell Oskay - subscribing you to this report since this Inkscape
regression affects 'Hershey Text' (now included with inkscape trunk) as
well as the 'Eggbot Control' extension.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape
@~suv
Thank you for the notice, and for verifying the cause. This issue (crashing
with an empty param) does not seem to affect Inkscape prior to 0.48.4.
@Hans Schepker (hschepker)
Would have appreciated you filing the bug report with the Eggbot project
directly, so that we could have gotten
** Information type changed from Private to Public
** Also affects: inkscape
Importance: Undecided
Status: New
** Tags added: crash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
** Tags added: extensions-plugins
** Changed in: inkscape
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1204732
Title:
inkscape crashed with
Reproduced eggbot extension with Inkscape 0.48.4 and 0.48+devel r12442
on OS X 10.7.5 - if using Inkscape with most recent versions of
dependencies (same inkscape versions compiled and running with older
versions of dependencies do not crash):
$ port installed glib2 glibmm gtk2 gtkmm gettext
Crash not reproduced on OS X 10.7.5 with these versions of dependencies
(same Inkscape versions, same eggbot extension installation):
$ port installed glib2 glibmm gtk2 gtkmm gettext intltool libsigcxx2 | grep
active
gettext @0.18.1.1_2 (active)
glib2 @2.32.4_0+debug_symbols (active)
24 matches
Mail list logo
