Red Hat Bugzilla – Bug 1027175
[abrt] darktable-1.2.3-1.fc19: dt_accel_deregister_iop: Process /usr/bin/darktable was killed by signal 6 (SIGABRT)
Last modified: 2014-09-14 20:04:31 EDT
Description of problem: Crash when saving new preset for exposure plug-in. reproducible: randomly Version-Release number of selected component: darktable-1.2.3-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/darktable /home/martix/data/100CANON/Magda/TIF/IMG_4223.TIF /home/martix/data/100CANON/Magda/TIF/IMG_4231.TIF /home/martix/data/100CANON/Magda/TIF/IMG_4273.TIF /home/martix/data/100CANON/Magda/TIF/IMG_4291.TIF /home/martix/data/100CANON/Magda/TIF/IMG_4376.TIF crash_function: dt_accel_deregister_iop executable: /usr/bin/darktable kernel: 3.11.6-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 dt_accel_deregister_iop at /usr/bin/../lib64/darktable/libdarktable.so #6 dt_accel_rename_preset_iop at /usr/bin/../lib64/darktable/libdarktable.so #7 edit_preset_response at /usr/bin/../lib64/darktable/libdarktable.so #8 g_cclosure_marshal_VOID__INTv at gmarshal.c:410 #9 _g_closure_invoke_va at gclosure.c:840 #15 gtk_real_button_released at /lib64/libgtk-x11-2.0.so.0 #16 _g_closure_invoke_va at gclosure.c:840 #19 gtk_button_button_release at /lib64/libgtk-x11-2.0.so.0 #20 _gtk_marshal_BOOLEAN__BOXED at /lib64/libgtk-x11-2.0.so.0 #25 gtk_widget_event_internal at /lib64/libgtk-x11-2.0.so.0
Created attachment 820274 [details] File: backtrace
Created attachment 820275 [details] File: cgroup
Created attachment 820276 [details] File: core_backtrace
Created attachment 820277 [details] File: dso_list
Created attachment 820278 [details] File: environ
Created attachment 820279 [details] File: limits
Created attachment 820280 [details] File: maps
Created attachment 820281 [details] File: open_fds
Created attachment 820282 [details] File: proc_pid_status
I don't seem to have this bug in darktable 1.4. It's available in the updates-testing repository if you want to give it a try. Please re-open this bug if problem persists with 1.4. Thank you for your report.