GNOME Bugzilla – Bug 636956
[abrt] evolution-data-server-2.32.1-1.fc14: (SIGSEGV) authenticate, gdata_service_authenticate, e_book_backend_google_authenticate_user
Last modified: 2012-09-04 19:06:16 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=661692 abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/e-addressbook-factory component: evolution-data-server crash_function: authenticate executable: /usr/libexec/e-addressbook-factory kernel: 2.6.35.9-64.fc14.x86_64 package: evolution-data-server-2.32.1-1.fc14 rating: 4 reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1291897433 uid: 500 How to reproduce ----- I'm not sure how to actually reproduce it, but here is what I did this time: 1. crash evolution 2. start evolution 3. recover open drafts Core was generated by `/usr/libexec/e-addressbook-factory'. Program terminated with signal 11, Segmentation fault.
+ Trace 225075
Thread 6 (Thread 2546)
Thread 2 (Thread 2541)
Thread 1 (Thread 2538)
What version of libgdata is this with?
That probably was with libgdata version 0.6.4-4.fc14 Thanks.
I'm not quite sure how this could've happened. It looks like the GDataService instance being passed to gdata_service_authenticate() is NULL, which indicates a bug in the Google Contacts e-d-s backend (rather than libgdata). The only way I can think of that this could've happened, however, is for e_book_backend_google_set_mode() to have been called from another thread to set the backend to offline mode, while the thread that crashed was between lines 1037 and 1046 of e-book-backend-google.c. Milan, does that sound possible? I don't know enough about the interactions between threads in synchronous address book backends to be able to say.
It's done semi-asynchronously, so it's also possible that the backend was freed or manipulated before the authentication got to the processing. I do not think the libgdata is causing this, so I filled this against eds.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.