Version-Release number of selected component: evolution-3.10.4-3.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: evolution crash_function: sync_created_items executable: /usr/bin/evolution kernel: 3.15.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 sync_created_items at camel-ews-folder.c:1356 #1 ews_refresh_info_sync at camel-ews-folder.c:1546 #2 camel_folder_refresh_info_sync at camel-folder.c:4209 #3 folder_refresh_info_thread at camel-folder.c:1465 #4 run_in_thread at gsimpleasyncresult.c:871 #5 io_job_thread at gioscheduler.c:89 #6 g_task_thread_pool_thread at gtask.c:1245 #8 g_thread_proxy at gthread.c:798
Created attachment 927595 [details] File: backtrace
Created attachment 927596 [details] File: cgroup
Created attachment 927597 [details] File: core_backtrace
Created attachment 927598 [details] File: dso_list
Created attachment 927599 [details] File: environ
Created attachment 927600 [details] File: exploitable
Created attachment 927601 [details] File: limits
Created attachment 927602 [details] File: maps
Created attachment 927603 [details] File: open_fds
Created attachment 927604 [details] File: proc_pid_status
Created attachment 927605 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace where and why the evolution-ews crashed, but I do not see the actual reason of it. The var_log_messages suggest that you've lost a connection while the EWS account was updating itself. Could that be the reason/circumstance, which caused the crash, please? I can easily workaround the actual crash by adding safety checks to the code, but it can cause other side effects, thus I'd rather know the crash reason first. Ideally if you would be able to reproduce it, to give some clues what was happening there.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days