Description of problem: Control - a to select everything in inbox. Control - y . Evolution crash Version-Release number of selected component: evolution-3.16.5-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: ews_update_mgtrequest_mime_calendar_itemid executable: /usr/bin/evolution global_pid: 2668 kernel: 4.1.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ews_update_mgtrequest_mime_calendar_itemid at camel-ews-folder.c:440 #1 camel_ews_folder_get_message at camel-ews-folder.c:631 #2 ews_folder_get_message_sync at camel-ews-folder.c:733 #3 camel_folder_get_message_sync at camel-folder.c:3037 #4 get_message_cb at camel-filter-driver.c:1621 #5 camel_filter_search_get_message at camel-filter-search.c:135 #6 junk_test at camel-filter-search.c:941 #7 camel_sexp_term_eval at camel-sexp.c:808 #8 camel_sexp_eval at camel-sexp.c:1722 #9 camel_filter_search_match at camel-filter-search.c:1148
Created attachment 1070072 [details] File: backtrace
Created attachment 1070073 [details] File: cgroup
Created attachment 1070074 [details] File: core_backtrace
Created attachment 1070075 [details] File: dso_list
Created attachment 1070076 [details] File: environ
Created attachment 1070077 [details] File: limits
Created attachment 1070078 [details] File: maps
Created attachment 1070079 [details] File: mountinfo
Created attachment 1070080 [details] File: namespaces
Created attachment 1070081 [details] File: open_fds
Created attachment 1070082 [details] File: proc_pid_status
Created attachment 1070083 [details] File: var_log_messages
Thanks for a bug report. I see in the backtrace that this crashed when reading one of your messages, namely a meeting invitation. It seems like the message had missing or garbled the internal calendar component for some reason. Could you check the content of /home/steve/.cache/evolution/mail/1398693974.13391.6.com/folders/Inbox/mimecontent/KAAI3X please? Maybe it'll be missing, due to some cleanup the next evolution start, thus if you manage to reproduce the crash, then see the backtrace and search for the same path, but a different file name. The content will show what the message had included possibly why the calendar component failed to be created. It's quite easy to check for the return value and skip the crashing code if certain parts fail, but I'd like to figure out the reason why it failed, whether it's a valid state or an issue in the code, possibly in a different place. Thanks in advance.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.