Inkscape crashed with SIGSEGV when saving drawing for first time

[John Stevenson]

I created a new drawing with a copule of text boxes and three objects - two copied from the original - which was an intersection of two rounded boxes.

The document saved successfully and then I got a message popup that there had been an error with Inkscape and had to close. I was able to open the document in inkscape after I selected to restart Inkscape.

I am using Ubuntu 12.04, last updated mid April.

Inkscape version 0.48.3.1-1ubuntu1

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
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Sun Apr 22 11:37:45 2012
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: inkscape
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f02445f8390: movzbl (%rsi),%ecx
 PC (0x7f02445f8390) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: inkscape crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 completion_match_func (comp=<optimized out>, key_unused=<optimized out>, iter=<optimized out>, data=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkfilechooserentry.c:427
 gtk_entry_completion_visible_func (model=<optimized out>, iter=0x7fff94e081d0, data=0x994f5b0) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkentrycompletion.c:821
 gtk_tree_model_filter_visible (filter=<optimized out>, child_iter=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtktreemodelfilter.c:764
 gtk_tree_model_filter_build_level (filter=0x6bfc0d0, parent_level=<optimized out>, parent_elt_index=<optimized out>, emit_inserted=0) at /build/buildd/gtk+2.0-2.24.10/gtk/gtktreemodelfilter.c:535
 gtk_tree_model_filter_iter_n_children (model=0x6bfc0d0, iter=0x0) at /build/buildd/gtk+2.0-2.24.10/gtk/gtktreemodelfilter.c:2599

[Bryce Harrington (bryce)]

I think this may not be an Inkscape bug. It looks like the crash is happening in the file chooser code due to trying to do a string comparison against either an undefined string or a file named with unicode characters ("\240\371V\b")

> Thread 1 (Thread 0x7f024bbcb9c0 (LWP 31756)):
> #0 __strncmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:1738
> No locals.
> #1 0x00007f024994de68 in completion_match_func (comp=<optimized out>, key_unused=<optimized out>, iter=<optimized out>, data=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkfilechooserentry.c:427
> chooser_entry = <optimized out>
> name = 0x947c550 "\240\371V\b"
> result = <optimized out>
> norm_file_part = 0x995c2c0 "\001"
> norm_name = 0x0
> #2 0x00007f0249931b0a in gtk_entry_completion_visible_func (model=<optimized out>, iter=0x7fff94e081d0, data=0x994f5b0) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkentrycompletion.c:821
> ret = 0
> completion = 0x994f5b0
> #3 0x00007f0249a796ee in gtk_tree_model_filter_visible (filter=<optimized out>, child_iter=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtktreemodelfilter.c:764

Anyway, I'm not even sure there's anything we could do to work around this in Inkscape.

[Max Gaukler (mgmax)]

Does the bug still happen with the latest inkscape version (0.92.3)?

[Qantas94Heavy (qantas94heavy)]

Closing as I can't reproduce with Inkscape 0.92.4 on openSUSE TW 20190411 and there has been no response for over 30 days. If you still have a similar issue, please report it here: https://inkscape.org/report. Thank you!

Closed by: https://gitlab.com/Qantas94Heavy