Crashes after a couple minutes no matter what you are doing.

[t.w.march]

One 2 different systems, one intel and one nvidia graphics, after a couple minutes running a popup window show up with nothing in it and inscape has crashed. If you pass any window over it it will clear the window. If i run in in a terminal it will tell me:

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.

Inkscape .91

System :FreeBSD 10.1-RELEASE-p23 FreeBSD 10.1-RELEASE-p23 #0: Thu May 14 13:35:13 UTC 2015 <email address hidden>:/usr/obj/usr/src/sys/GENERIC amd64

=====
FreeBSD Inkscape package info:
http://portsmon.freebsd.org/portoverview.py?category=graphics&portname=inkscape
http://svnweb.freebsd.org/ports/head/graphics/inkscape/Makefile?revision=385075&view=markup

[su_v (suv-lp)]

Which desktop environment and gtk2 theme/theme engine do you use?

Based on the description of the crash, this sounds very similar to a known upstream bug in the qt-curve theme engine for GTK2, tracked for Inkscape in:
* Bug #1422479 “Crash under Plasma5 an qtcurve”
  https://bugs.launchpad.net/inkscape/+bug/1422479

--
<off-topic>
Unfortunately, I don't know how to "process" a binary truss file locally (further triage of the report will have to wait until on of the core devs happens to encounter a similar crash on a FreeBSD-based system, I guess) - any chance you could provide a "normal" backtrace of the crash instead, ideally with debug symbols installed?
</off-topic>

[t.w.march (t-w-march)]

I am using KDE 4.14.3 on both computers that this is happening to. It was working fine until we upgraded to .91. I am trying to figure out if i am using that theme, but I can't find the files they are talking about.

[t.w.march (t-w-march)]

I tried a couple different gtk themes and I get the same result.

[su_v (suv-lp)]

Which theme engines (not themes) did you test?

Does the crash happen with stock GTK2 theme 'Raleigh' too?

[t.w.march (t-w-march)]

Yeah, I ran gdb while running 'Raleigh' and I get the same result.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 811c06400 (LWP 100722/inkscape)]
0x000000080a23a3c0 in strcmp () from /lib/libc.so.7

[su_v (suv-lp)]

Any chance you could provide a full backtrace?

[t.w.march (t-w-march)]

Something funny is happening. I did change the gtk-theme to raleigh, but it looks like inscape is still calling qtcurve. I even made sure to reboot the computer to make sure that kde was fully restarted.

#0 0x000000080a23a3c0 in strcmp () from /lib/libc.so.7
No symbol table info available.
#1 0x00000008120128e2 in qtcurve_style_class_init ()
   from /usr/local/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
No symbol table info available.
#2 0x00000000007e9fbc in Gtk::CellLayout::pack_start<Glib::ustring> ()
No symbol table info available.
#3 0x000000080269b1a0 in _gtk_marshal_BOOLEAN__BOXED ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#4 0x0000000808dad901 in g_closure_invoke ()
   from /usr/local/lib/libgobject-2.0.so.0
No symbol table info available.
#5 0x0000000808dc2073 in g_signal_emitv ()
   from /usr/local/lib/libgobject-2.0.so.0
No symbol table info available.
#6 0x0000000808dc2c32 in g_signal_emit_valist ()
   from /usr/local/lib/libgobject-2.0.so.0
No symbol table info available.
#7 0x0000000808dc3294 in g_signal_emit ()
   from /usr/local/lib/libgobject-2.0.so.0
No symbol table info available.
#8 0x00000008027be8d6 in gtk_widget_event ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#9 0x0000000802698ecc in gtk_main_do_event ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#10 0x0000000802bb5f84 in _gdk_window_process_updates_recurse ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#11 0x0000000802bb5ec5 in _gdk_window_process_updates_recurse ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#12 0x0000000802bb5ec5 in _gdk_window_process_updates_recurse ()
---Type <return> to continue, or q <return> to quit---
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#13 0x0000000802bb5ec5 in _gdk_window_process_updates_recurse ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#14 0x0000000802bb5ec5 in _gdk_window_process_updates_recurse ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#15 0x0000000802bb5ec5 in _gdk_window_process_updates_recurse ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#16 0x0000000802bb69b5 in gdk_window_process_all_updates ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#17 0x0000000802bb646d in gdk_window_process_all_updates ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#18 0x0000000802616790 in _gtk_container_queue_resize ()
   from /usr/local/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#19 0x0000000802b94815 in gdk_threads_add_idle_full ()
   from /usr/local/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#20 0x0000000809033592 in g_main_context_dispatch ()
   from /usr/local/lib/libglib-2.0.so.0
No symbol table info available.
#21 0x00000008090338e7 in g_main_context_pending ()
   from /usr/local/lib/libglib-2.0.so.0
No symbol table info available.
#22 0x0000000809033bff in g_main_loop_run ()
   from /usr/local/lib/libglib-2.0.so.0
No symbol table info available.
#23 ...

[su_v (suv-lp)]

On 2015-05-25 06:20 (+0200), t.w.march wrote:
> Something funny is happening. I did change the gtk-theme to raleigh, but
> it looks like inscape is still calling qtcurve. I even made sure to
> reboot the computer to make sure that kde was fully restarted.
(...)
> Is there another way to see what module is actually loading besides the
> kde module? it does seem to be changing the look of my gtk applications,
> but maybe (i am grasping at straws) it isn't changing the config files
> fully

Sorry for the delayed response. That question isn't really specific to inkscape, and unfortunately I can't answer it.

Overall, it seems that you encountered an upstream bug in the custom gtk2 theme engine (qtcurve) as mentioned earlier.
Other similar reports filed for Inkscape so far are: bug #1422479, bug #1463877, bug #1469727.

This comment has links to upstream reports at the time (June 2015):
https://bugs.launchpad.net/inkscape/+bug/1469727/comments/4

Any information whether there had been a new release of the theme engine in the meantime which includes a fix would be appreciated.

[Qantas94Heavy (qantas94heavy)]

As mentioned in comment 9, this appears to be a upstream qtcurve bug rather than an issue with Inkscape itself.