GNOME Bugzilla – Bug 675730
[abrt] Crash on book backend regular update
Last modified: 2012-08-20 17:21:55 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=820069 [abrt] evolution-data-server-3.4.1-2.fc17: Process /usr/libexec/evolution-addressbook-factory was killed by signal 11 (SIGSEGV) libreport version: 2.0.10 abrt_version: 2.0.10 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory core_backtrace: crash_function: e_ews_connection_sync_folder_items_start executable: /usr/libexec/evolution-addressbook-factory kernel: 3.3.4-1.fc17.i686.PAE time: Пт. 04 мая 2012 10:01:59 Core was generated by `/usr/libexec/evolution-addressbook-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 230198
Thread 1 (Thread 0xb3afdb40 (LWP 32026))
Also seen with evolution-data-server-3.4.4-1.fc17. For what it's worth, I had no connection to the EWS server when this happened. Perhaps that's related.
You are right, it's related. The connection argument passed in as 'cnc' is NULL, thus it crashes when the code tries to dereference it. I'll check what I can do with it.
Created attachment 221859 [details] [review] ews patch for evolution-ews; I think there is nothing better to be done than postponing the scheduled update, if the backend is not connected currently.
Created commit 87be19d in ews master (3.5.91+)