Inkscape crash on color palettes hover (qtcurve).

[Tiago Pires]

Description: Inkscape crashes the moment the mouse cursor moves over the color palettes panel.

Error: “inkscape ” terminated by signal SIGSEGV (Address boundary error).

Software: extra/inkscape 0.91-9
OS: Arch Linux x86_64
Kernel: 4.0.5-1-ARCH
DE: KDE
GTK2 theme: QtCurve
GTK2 font name: Roboto 11
RAM: 3186M / 7770M (41%)
SWAP: 252M / 8190M (3%)
CPU: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz
Root: 29G / 32G (95%) (ext4)

[su_v (suv-lp)]

On 2015-06-10 17:04 (+0200), Tiago Pires wrote:
> DE: KDE
> GTK2 theme: QtCurve

Any chance you could attach a backtrace of the crash?
Does the same crash occur if you switch the theme for GTK2 applications e.g. to 'Raleigh'?

[Tiago Pires (aero-glass)]

I do not have Raleigh available however changing the GTK2 theme prevented the crash.
The GTK2 theme I was using is designed to make GTK2 applications conform to my KDE widget style and color scheme.
So far this is the only application that has presented any bugs as a result of using this theme.
It would be really great if someone could offer some advice on how to fix this for Inkscape.

Please see below for the backtrace:

(inkscape:4955): GLib-GObject-WARNING **: gsignal.c:2451: signal 'child-added' is invalid for instance '0x3e248f0' of type 'GtkMenu'
[New Thread 0x7fffe0f5b700 (LWP 5022)]
[New Thread 0x7fffe2db3700 (LWP 5021)]
[New Thread 0x7fffe35b4700 (LWP 5020)]

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe4013d71 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
(gdb) thread apply all backtrace

Thread 11 (Thread 0x7fffe35b4700 (LWP 5020)):
#0 0x00007ffff0cc7939 in syscall () from /usr/lib/libc.so.6
#1 0x00007ffff1dfd67a in g_cond_wait_until () from /usr/lib/libglib-2.0.so.0
#2 0x00007ffff1d8d889 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x00007ffff1d8deab in g_async_queue_timeout_pop () from /usr/lib/libglib-2.0.so.0
#4 0x00007ffff1de007c in ?? () from /usr/lib/libglib-2.0.so.0
#5 0x00007ffff1ddf625 in ?? () from /usr/lib/libglib-2.0.so.0
#6 0x00007ffff0f8d354 in start_thread () from /usr/lib/libpthread.so.0
#7 0x00007ffff0ccbbfd in clone () from /usr/lib/libc.so.6

Thread 10 (Thread 0x7fffe2db3700 (LWP 5021)):
#0 0x00007ffff0cc2e8d in poll () from /usr/lib/libc.so.6
#1 0x00007ffff1db8c7c in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007ffff1db9002 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#3 0x00007ffff071f876 in ?? () from /usr/lib/libgio-2.0.so.0
#4 0x00007ffff1ddf625 in ?? () from /usr/lib/libglib-2.0.so.0
#5 0x00007ffff0f8d354 in start_thread () from /usr/lib/libpthread.so.0
#6 0x00007ffff0ccbbfd in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7fffe0f5b700 (LWP 5022)):
#0 0x00007ffff0cc2e8d in poll () from /usr/lib/libc.so.6
#1 0x00007ffff1db8c7c in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007ffff1db8d8c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3 0x00007ffff1db8dc9 in ?? () from /usr/lib/libglib-2.0.so.0
#4 0x00007ffff1ddf625 in ?? () from /usr/lib/libglib-2.0.so.0
#5 0x00007ffff0f8d354 in start_thread () from /usr/lib/libpthread.so.0
#6 0x00007ffff0ccbbfd in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7fffe8a92700 (LWP 5009)):
#0 0x00007ffff0f9296f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007ffff5f41747 in ?? () from /usr/lib/libgc.so.1
#2 0x00007ffff5f377ef in ?? () from /usr/lib/libgc.so.1
#3 0x00007ffff5f3f917 in ?? () from /usr/lib/libgc.so.1
#4 0x00007ffff0f8d354 in start_thread () from /usr/lib/libpthread.so.0
#5 0x00007ffff0ccbbfd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7fffe8291700 (LWP 5010)):
#0 0x00007ffff0f9296f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#1 0x00007ffff5f41747 in ?? () from /usr/lib/libgc.so.1
#2 0x00007ffff5f377ef in ?? () from /usr/lib/libgc.so.1
#3 0x00007ffff5f3f917 in ?? () from /usr/lib/libgc.so.1
#4 0x00007...

[su_v (suv-lp)]

On 2015-06-10 21:15 (+0200), Tiago Pires wrote:
> I do not have Raleigh available however changing the GTK2 theme
> prevented the crash.
(…)
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007fffe4013d71 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so

Please report this crash in qtcurve's bug tracker.

Setting bug status for project 'Inkscape' to triaged for now - AFAICT nothing to be fixed in Inskcape, but if this is a yet another bug/regression in qtcurve affecting Inkscape badly, users with KDE or other Qt'-based DEs experiencing this Inkscape crash will likely search in Inkscape's bug tracker first (based on past experience).

[Qantas94Heavy (qantas94heavy)]

From other bug reports (e.g. bug #1422479), this is an issue with qtcurve which has now released a fix with qtcurve 1.9.0. As this is not an Inkscape bug, closing as invalid.