GNOME Bugzilla – Bug 756928
Segfault while sending / autoadd when remote contact server unavailable
Last modified: 2015-10-22 06:55:05 UTC
This is a particularly frustrating segfault bug due to the inability in this version (packaged for debian 8.2) to remove a contact source. Steps to duplicate: 1. Set up a connection to a remote contacts server. (google in my case) 2. Configure the remote contacts server to return a 403 error, or perhaps the programmer can just alter the database to connect to https://developers.google.com/accounts/docs/AuthForInstalledApps with bogus credentials. 3. Configure evolution to autoadd to a contact list on the bogus server. (this might not matter, but there seems to be some autoadd component involved) 4. Send an email to someone not in your address books. Watch evolution vanish. Sometimes the email makes it to the server, other times it seems to crash before then. Must be that the sending is in another thread. DUMP, with anything that could be identifying marked by [REDACTED]. ** (evolution:3011): WARNING **: bbdb: Failed to get addressbook client : Unable to connect to '[REDACTED]': The requested resource was not found: https://developers.google.com/accounts/docs/AuthForInstalledApps ** (evolution:3011): WARNING **: bbdb: Failed to get addressbook client : (null) (evolution:3011): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Create resource '[REDACTED]' failed with HTTP status 403 (Forbidden) ** (evolution:3011): WARNING **: bbdb: Failed to add new contact: (null) [Thread 0x7fff711ee700 (LWP 4150) exited] Program received signal SIGSEGV, Segmentation fault.
+ Trace 235603
Thread 140734589949696 (LWP 4155)
Thanks for a bug report. I hope you are aware you use pretty old version of the Evolution. This particular crash had been fixed almost 11 months ago. *** This bug has been marked as a duplicate of bug 734530 ***