Description of problem: Was executing Send/Receive when it crashed. Version-Release number of selected component: evolution-3.6.4-3.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: gtk_box_forall executable: /usr/bin/evolution kernel: 3.8.3-203.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_box_forall at gtkbox.c:1871 #1 gtk_container_get_children at gtkcontainer.c:2157 #2 gtk_box_get_path_for_child at gtkbox.c:913 #3 gtk_container_get_path_for_child at gtkcontainer.c:3425 #4 _gtk_widget_create_path at gtkwidget.c:13917 #5 gtk_container_real_get_path_for_child at gtkcontainer.c:2378 #6 gtk_frame_get_path_for_child at gtkframe.c:390 #7 gtk_container_get_path_for_child at gtkcontainer.c:3425 #8 _gtk_widget_create_path at gtkwidget.c:13917 #9 gtk_box_get_path_for_child at gtkbox.c:904
Created attachment 714810 [details] File: backtrace
Created attachment 714811 [details] File: build_ids
Created attachment 714812 [details] File: cgroup
Created attachment 714813 [details] File: core_backtrace
Created attachment 714814 [details] File: dso_list
Created attachment 714815 [details] File: environ
Created attachment 714816 [details] File: limits
Created attachment 714817 [details] File: maps
Created attachment 714818 [details] File: open_fds
Created attachment 714819 [details] File: proc_pid_status
Created attachment 714820 [details] File: smolt_data
Created attachment 714821 [details] File: var_log_messages
Thanks for a bug report. I tried to find anything similar upstream, but with no luck. I see in the backtrace this: > gtk_container_get_path_for_child (container=0x18d4470 [GtkHBox], > child=child@entry=0x2ce4470 [EActivityProxy]) but it doesn't give me much idea what could be wrong here. Is this happening for you often, after certain conditions, please? I hit Send/Receive every morning, and I do not recall ever seeing any crash like this (maybe I was only lucky).
I get infrequent crashes doing Send/Receives and I haven't been able to identify conditions that make the crash reproducible. I'll keep an eye on it and report more if I can get more information.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.