inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()

Bug #985412 reported by Jan Commandeur
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
High
Unassigned
inkscape (Ubuntu)
New
Medium
Unassigned

Bug Description

measurepath
lenghtunit mm
apply

secondtime i tried the crash came back

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: inkscape 0.48.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Thu Apr 19 07:36:44 2012
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120404)
ProcCmdline: /usr/bin/inkscape /home/username/Documenten/plattegrond_klif_8_nieuw.svg
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7cecd7 <_ZN8Inkscape9Extension14Implementation6Script6effectEPNS0_6EffectEPNS_2UI4View4ViewEPNS1_27ImplementationDocumentCacheE+839>: mov 0x1d8(%rax),%edi
 PC (0x007cecd7) ok
 source "0x1d8(%rax)" (0x000001d8) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
Stacktrace:
 #0 0x00000000007cecd7 in Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
 No symbol table info available.
 Cannot access memory at address 0x7fffe5fe0fa8
StacktraceTop: Inkscape::Extension::Implementation::Script::effect(Inkscape::Extension::Effect*, Inkscape::UI::View::View*, Inkscape::Extension::Implementation::ImplementationDocumentCache*) ()
ThreadStacktrace:
 .
 Thread 2 (LWP 2292):
 #0 0x00007fc523b1eb03 in ?? ()
 No symbol table info available.
 .
Title: inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jan Commandeur (jancommandeur) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: Inkscape::Extension::Implementation::Script::effect (this=0x1e67020, module=<optimized out>, doc=0x2c5dc00, docCache=<optimized out>) at extension/implementation/script.cpp:734

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in inkscape:
importance: Undecided → High
tags: added: crash extensions-plugins
Revision history for this message
su_v (suv-lp) wrote :

Duplicate of Bug #944077 "inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()"?

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "schermafdruk1.png" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
tags: removed: patch
Revision history for this message
su_v (suv-lp) wrote :

Linking as duplicate to Bug #944077 "inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()".
Please add a comment here and revert the duplicate status if you don't agree and think these are different issues.

(Note: the fix will be available in the next planned bug-fix release 0.48.4)

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.