Version-Release number of selected component: evolution-3.8.5-2.fc19 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: gtk_tree_view_get_selection executable: /usr/bin/evolution kernel: 3.14.7-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_tree_view_get_selection at gtktreeview.c:11468 #1 vfr_folder_response at em-vfolder-editor-rule.c:322 #6 _g_closure_invoke_va at gclosure.c:840 #9 gtk_real_button_released at gtkbutton.c:1973 #10 _g_closure_invoke_va at gclosure.c:840 #13 gtk_button_button_release at gtkbutton.c:1805 #14 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #15 _g_closure_invoke_va at gclosure.c:840 #18 gtk_widget_event_internal at gtkwidget.c:6721 #19 gtk_widget_event at gtkwidget.c:6378
Created attachment 910125 [details] File: backtrace
Created attachment 910126 [details] File: cgroup
Created attachment 910127 [details] File: core_backtrace
Created attachment 910128 [details] File: dso_list
Created attachment 910129 [details] File: environ
Created attachment 910130 [details] File: exploitable
Created attachment 910131 [details] File: limits
Created attachment 910132 [details] File: maps
Created attachment 910133 [details] File: open_fds
Created attachment 910134 [details] File: proc_pid_status
Created attachment 910135 [details] File: var_log_messages
Thanks for a bug report. I tried to fins anything similar in the upstream bugzilla, but no luck. Do you have any steps, how to reproduce it, please? I would to try it here, on a more recent code than 3.8.x, to see whether it's still an issue.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I am closing this bug. It was generated automatically on Fedora, and while we still get occasional Firefox crashes, I don't think we have enough data to justify following up, and this particular problem may well have been resolved in the current version of Firefox.
This bug is closed (see note). This bug applied to an earlier (non-current) release of Firefox, and there is no point in following up on it now.