Version-Release number of selected component: darktable-1.4.1-3.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: darktable crash_function: _dt_sigsegv_handler executable: /usr/bin/darktable kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 _dt_sigsegv_handler at /usr/src/debug/darktable-1.4.1/src/common/darktable.c:188 #3 gtk_widget_get_pointer at gtkwidget.c:8434 #4 dt_control_expose at /usr/src/debug/darktable-1.4.1/src/control/control.c:1278 #5 expose at /usr/src/debug/darktable-1.4.1/src/gui/gtk.c:469 #6 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #11 gtk_widget_event_internal at gtkwidget.c:5017 #12 gtk_widget_send_expose at gtkwidget.c:4846 #13 gtk_main_do_event at gtkmain.c:1621 #14 _gdk_window_process_updates_recurse at gdkwindow.c:5427 #16 _gdk_windowing_window_process_updates_recurse at gdkwindow-x11.c:5643
Created attachment 885923 [details] File: backtrace
Created attachment 885924 [details] File: cgroup
Created attachment 885925 [details] File: core_backtrace
Created attachment 885926 [details] File: dso_list
Created attachment 885927 [details] File: environ
Created attachment 885928 [details] File: exploitable
Created attachment 885929 [details] File: limits
Created attachment 885930 [details] File: maps
Created attachment 885931 [details] File: open_fds
Created attachment 885932 [details] File: proc_pid_status
Created attachment 885933 [details] File: var_log_messages
Any steps on how to reproduce this bug?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Can't reproduce this bug. Please feel free to reopen it if problem persists.