inkscape crashed with SIGSEGV when using calligraphy tool with a Wacom tablet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
inkscape (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: inkscape
When trying to change the "Draw calligraphic or brush strokes" preset drop list (No Preset|Dip pen|Marker|Brush) with a Wacom pen tip ("Wacom Intuos3 6x8"), a completely blank dialog window opens (sometimes, usually it crashes before that window has time to open) and Inkscape window crashes.
Terminal error messages:
> 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.
> Segmentation fault (core dumped)
It only happens when stylus is set to Screen mode (normal mode, the most often used), not if it is set to Window mode in Inkscape's Files>Input devices.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Sep 16 17:02:14 2009
Disassembly: 0x5e6f3e: Cannot access memory at address 0x5e6f3e
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/inkscape
NonfreeKernelMo
Package: inkscape 0.47~pre1-0ubuntu2
ProcCmdline: inkscape
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x5e6f3e: Cannot access memory at address 0x5e6f3e
PC (0x005e6f3e) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: inkscape
Stacktrace:
#0 0x005e6f3e in ?? ()
No symbol table info available.
Cannot access memory at address 0xbff8e1c0
StacktraceTop: ?? ()
ThreadStacktrace:
.
Thread 1 (Thread 2878):
#0 0x005e6f3e in ?? ()
No symbol table info available.
Cannot access memory at address 0xbff8e1c0
Title: inkscape crashed with SIGSEGV
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
visibility: | private → public |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The backtrace you attached doesn't contain any debugging symbols, so please could you try to obtain a new backtrace by following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.