Version-Release number of selected component: darktable-1.2.3-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /bin/darktable crash_function: _g_log_abort executable: /usr/bin/darktable kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 miUnionNonO at gdkregion-generic.c:1110 #6 miRegionOp at gdkregion-generic.c:1021 #7 gdk_region_union at gdkregion-generic.c:1266 #8 gdk_window_invalidate_maybe_recurse_full at gdkwindow.c:5986 #10 gdk_window_invalidate_region_full at gdkwindow.c:6041 #11 gdk_window_invalidate_rect_full at gdkwindow.c:5823 #12 gdk_window_invalidate_rect at gdkwindow.c:5843 #13 gtk_widget_queue_draw_area at gtkwidget.c:3713 #14 gtk_widget_queue_draw at gtkwidget.c:3783
Created attachment 844750 [details] File: backtrace
Created attachment 844751 [details] File: cgroup
Created attachment 844752 [details] File: core_backtrace
Created attachment 844753 [details] File: dso_list
Created attachment 844754 [details] File: environ
Created attachment 844755 [details] File: limits
Created attachment 844756 [details] File: maps
Created attachment 844757 [details] File: open_fds
Created attachment 844758 [details] File: proc_pid_status
Created attachment 844759 [details] File: var_log_messages
Any idea on how to reproduce this crash?