inkscape crashed with SIGSEGV in g_main_context_dispatch()

Bug #1505106 reported by Luca Ciavatta
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
inkscape (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) Ubuntu 15.04
2) inkscape 0.91-3ubuntu1
3) I saved my works, overwriting some svg files
4) After Inkscape saved the files, issue report was showed and Inkscape crashed

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: inkscape 0.91-3ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Oct 12 09:16:59 2015
ExecutablePath: /usr/bin/inkscape
InstallationDate: Installed on 2015-05-08 (156 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: inkscape /home/username/.icons/Tear\ Icons/apps/scalable/xchat.svg
SegvAnalysis:
 Segfault happened at: 0x504c92: mov 0x10(%rax),%rax
 PC (0x00504c92) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: inkscape crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Luca Ciavatta (cialu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1504807, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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