Version-Release number of selected component: shotwell-0.15.1-1.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: shotwell /run/media/andrea/3065-3637/DCIM/100MEDIA/PTDC0015.JPG crash_function: gtk_tree_model_filter_row_deleted executable: /usr/bin/shotwell kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_model_filter_row_deleted at gtktreemodelfilter.c:2584 #5 gtk_tree_model_row_deleted at gtktreemodel.c:1867 #6 emit_row_deleted_for_row at gtkfilesystemmodel.c:331 #7 remove_file at gtkfilesystemmodel.c:1912 #8 gtk_file_system_model_monitor_change at gtkfilesystemmodel.c:1257 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:522 #11 g_cclosure_marshal_generic_va at gclosure.c:1550 #12 _g_closure_invoke_va at gclosure.c:840 #15 emit_cb at gfilemonitor.c:392
Created attachment 890349 [details] File: backtrace
Created attachment 890350 [details] File: cgroup
Created attachment 890351 [details] File: core_backtrace
Created attachment 890352 [details] File: dso_list
Created attachment 890353 [details] File: environ
Created attachment 890354 [details] File: exploitable
Created attachment 890355 [details] File: limits
Created attachment 890356 [details] File: maps
Created attachment 890357 [details] File: open_fds
Created attachment 890358 [details] File: proc_pid_status
Created attachment 890359 [details] File: var_log_messages
This seems like a problem in Gtk3. There are many bugs with the same backtrace in different programs. This might be related: https://mail.gnome.org/archives/commits-list/2012-November/msg00502.html https://mail.gnome.org/archives/commits-list/2011-February/msg05789.html https://mail.gnome.org/archives/gtk-app-devel-list/2014-March/msg00064.html
*** Bug 1010739 has been marked as a duplicate of this bug. ***
*** Bug 1110493 has been marked as a duplicate of this bug. ***
*** Bug 1063046 has been marked as a duplicate of this bug. ***
See also bug 997255 and bug 1047322 that were closed by the original components. But the backtrace is the same.
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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.