Version-Release number of selected component: evolution-data-server-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: book_backend_google_get_backend_property executable: /usr/libexec/evolution-addressbook-factory kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 book_backend_google_get_backend_property at e-book-backend-google.c:1447 #1 data_book_constructed at e-data-book.c:1652 #2 g_object_new_internal at gobject.c:1785 #3 g_object_new_valist at gobject.c:2002 #4 g_initable_new_valist at ginitable.c:227 #5 g_initable_new at ginitable.c:149 #6 e_data_book_new at e-data-book.c:1846 #7 data_book_factory_open at e-data-book-factory.c:360 #8 data_book_factory_handle_open_address_book_cb at e-data-book-factory.c:417 #9 ffi_call_unix64 at ../src/x86/unix64.S:76
Created attachment 896359 [details] File: backtrace
Created attachment 896360 [details] File: cgroup
Created attachment 896361 [details] File: core_backtrace
Created attachment 896362 [details] File: dso_list
Created attachment 896363 [details] File: environ
Created attachment 896364 [details] File: exploitable
Created attachment 896365 [details] File: limits
Created attachment 896366 [details] File: maps
Created attachment 896367 [details] File: open_fds
Created attachment 896368 [details] File: proc_pid_status
Created attachment 896369 [details] File: var_log_messages
Thanks for a bug report. I do not see what could cause the crash in the backtrace, unfortunately, but I guess there happened some sort of memory corruption, like when a code accesses some already freed memory. Maybe this is related to bug #1082733 or bug #1064034, but I cannot tell for sure. By any chance, do you have any steps or anything, what would help to identify the cause of the crash, please?
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.