Crash under Plasma5 an qtcurve

[sebafroh]

Inkscape crashes after 1 to 20 seconds, showing an empty message-dialog, and exits with sigsegv. Crash seems not to be depending on user action, means it happends without reference to user-interaction. This crash happends evere time Inkscape is started!

System: actual ArchLinux (16.2.2015) with Plasma 5.2, qtcurve qtcurve-gtk2 1.8.18-3.

Bugtrace is:

 gdb inkscape
GNU gdb (GDB) 7.8.2
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inkscape...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/inkscape
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe8b3d700 (LWP 14998)]
[New Thread 0x7fffe833c700 (LWP 14999)]
[New Thread 0x7fffe7b3b700 (LWP 15000)]
[New Thread 0x7fffe5404700 (LWP 15005)]
[New Thread 0x7fffdffff700 (LWP 15006)]

Program received signal SIGSEGV, Segmentation fault.
0x00007fffe617cd71 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
(gdb) bt
#0 0x00007fffe617cd71 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
#1 0x00000000007e06c6 in ?? ()
#2 0x00007ffff69aa89f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#3 0x00007ffff20ae255 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#4 0x00007ffff20bfe42 in ?? () from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff20c8265 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff20c89bf in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff6ac199c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00007ffff69a9622 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x00007ffff66063df in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#10 0x00007ffff6606385 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#11 0x00007ffff6606385 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#12 0x00007ffff6606385 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#13 0x00007ffff6606385 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#14 0x00007ffff6606385 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#15 0x00007ffff6602cc8 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#16 0x00007ffff6603618 in gdk_window_process_all_updates () from /usr/lib/libgdk-x11-2.0.so.0
#17 0x00007ffff692e9b1 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x00007ffff65e2517 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#19 0x00007ffff1dd991d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0x00007ffff1dd9cf8 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0x00007ffff1dda022 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#22 0x00007ffff69a83f7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#23 0x00000000004742bc in ?? ()
#24 0x00007ffff0c96800 in __libc_start_main () from /usr/lib/libc.so.6
#25 0x00000000004708bf in ?? ()
(gdb)

[su_v (suv-lp)]

Please report this to the developers of qtcurve too.

[su_v (suv-lp)]

… and please add information about the version of Inkscape which was used to create the backtrace to the bug description.

[sebafroh (unrath)]

Inkscape Version is Inkscape 0.91 r13725 (Feb 9 2015). It is the third update of 0.91 arch has, but all where affected.

[sebafroh (unrath)]

Reportet to qtcurve.

https://bugs.kde.org/show_bug.cgi?id=344264

[sebafroh (unrath)]

Tryed it with another theme-engine (raleigh), there Inkscape seens to run stable. Maybe really a qtcurve-bug.

[Yichao Yu (yuyichao)]

Should be fixed in master.

The ArchLinux bug tracker[1] also has a workaround.

[1] https://bugs.archlinux.org/task/43631

[su_v (suv-lp)]

Thanks for reporting this upstream in KDE for qtcurve.

Setting bug status for project 'Inkscape' to 'Triaged' for now (so that affected users can find the report) - can be closed as 'Invalid' (not a bug in Inkscape) once a new version of qtcurve is released which includes the mentioned fix.

[sebafroh (unrath)]

Bug is fixed. See https://bugs.kde.org/show_bug.cgi?id=343704

[su_v (suv-lp)]

On 2015-03-25 20:53 (+0100), sebafroh wrote:
> Bug is fixed. See https://bugs.kde.org/show_bug.cgi?id=343704

It the fix available for users in stable qtcurve releases / updates on all main distros?

> ** Changed in: inkscape
> Status: Triaged => Fix Committed

No - reverting bug status change: there was no related commit in project 'Inkscape' (not needed either for project 'Inkscape' - as far as we know this is an upstream bug).

[su_v (suv-lp)]

Closing as 'Invalid' for project Inkscape - not an inkscape bug; no further feedback was provided by affected users about status of qt-curve releases available with main distros, either.