Version-Release number of selected component: darktable-1.2.2-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: darktable crash_function: miUnionNonO executable: /usr/bin/darktable kernel: 3.10.4-300.fc19.x86_64 runlevel: N 5 uid: 502 Truncated backtrace: Thread no. 1 (10 frames) #4 miUnionNonO at gdkregion-generic.c:1110 #5 miRegionOp at gdkregion-generic.c:1021 #6 gdk_region_union at gdkregion-generic.c:1266 #7 gdk_window_invalidate_maybe_recurse_full at gdkwindow.c:5986 #8 gtk_widget_size_allocate at gtkwidget.c:4133 #9 gtk_box_size_allocate at gtkbox.c:500 #10 g_cclosure_marshal_VOID__BOXEDv at gmarshal.c:1160 #11 _g_closure_invoke_va at gclosure.c:840 #14 gtk_widget_size_allocate at gtkwidget.c:4122 #15 gtk_box_size_allocate at gtkbox.c:500
Created attachment 782557 [details] File: backtrace
Created attachment 782558 [details] File: cgroup
Created attachment 782559 [details] File: core_backtrace
Created attachment 782560 [details] File: dso_list
Created attachment 782561 [details] File: environ
Created attachment 782562 [details] File: limits
Created attachment 782563 [details] File: maps
Created attachment 782564 [details] File: open_fds
Created attachment 782565 [details] File: proc_pid_status
Created attachment 782566 [details] File: var_log_messages
Please could you tell me how to reproduce this bug?
Another user experienced a similar problem: It happens when I have tried to delete one picture (from the database and from the storage, too). It happens after few succesful deletions of other images. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/darktable crash_function: miUnionNonO executable: /usr/bin/darktable kernel: 3.12.7-200.fc19.x86_64 package: darktable-1.4-1.fc19 reason: darktable killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
I can't reproduce. Is it still happening with darktable-1.6.0?
I can't reproduce it in darktable-1.6.0, either. It is not happening with current version of darktable, I think this bugreport could be closed.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.