Bug 707049

Summary: [abrt] evolution-data-server-2.32.2-1.fc14: __pthread_mutex_lock: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Robert Keersse <robert.keersse>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:554898ab430c548dd668d0b7463b29770436b4ae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-24 09:15:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Robert Keersse 2011-05-23 20:21:28 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 29130 bytes
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
Attached file: coredump, 46108672 bytes
crash_function: __pthread_mutex_lock
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.13-91.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1306138889
uid: 500

How to reproduce
-----
1.???
2.
3.

Comment 2 Milan Crha 2011-05-24 05:46:19 UTC
Thanks for a bug report. This seems to be related to bug #706539, on the first look. The backtrace is exposing your Google password, unfortunately, thus I suggest you to change it. I'm sorry for that.

Thread 1 (Thread 0x7f46de97a700 (LWP 23698)):
#0  __pthread_mutex_lock (mutex=0x0) at pthread_mutex_lock.c:50
#1  0x0000003603e32136 in soup_message_queue_append (queue=0x7f46c8001b00, msg=<value optimized out>, callback=0, user_data=0x0) at soup-message-queue.c:120
#2  0x0000003603e3706e in queue_message (session=0x7f46d401ae20, msg=0x7f46d0084620 [SoupMessage], callback=0, user_data=0x0) at soup-session.c:1472
#3  0x0000003603e3b8c0 in send_message (session=0x7f46d401ae20, msg=0x7f46d0084620 [SoupMessage]) at soup-session-sync.c:361
#4  0x000000358a01a1b4 in authenticate (self=0x7f46d4007d40, username=0x7f46d0001e50 "user", password=0xb7e9f0 "pass", captcha_token=<value optimized out>, captcha_answer=<value optimized out>, cancellable=0x0, error=0x7f46de979cc8) at gdata/gdata-service.c:603
#5  0x000000358a01adf5 in gdata_service_authenticate (self=<value optimized out>, username=<value optimized out>, password=<value optimized out>, cancellable=<value optimized out>, error=<value optimized out>) at gdata/gdata-service.c:812
#6  0x00007f46e0e56fa9 in e_book_backend_google_authenticate_user (backend=0xb99200 [EBookBackendGoogle], book=<value optimized out>, opid=<value optimized out>, username=<value optimized out>, password=0xb7e9f0 "pass", auth_method=<value optimized out>, perror=0x7f46de979d38) at e-book-backend-google.c:1046
#7  0x0000003c00e13479 in _e_book_backend_authenticate_user (backend=0xb99200 [EBookBackendGoogle], book=0xb9d300 [EDataBook], opid=14, user=0xbb32c0 "user", passwd=<value optimized out>, auth_method=<value optimized out>) at e-book-backend-sync.c:472

Comment 3 Milan Crha 2011-05-24 09:15:56 UTC
I've an update from the upstream developer and he said it is possible that this is a duplicate of the previous bug report, it might be caused by same issue, only the exact place where this crashed is in a different place. I'm marking this as a duplicate of the other bug because he said that this is about disappearing soup session object, which just mean that it can crash in basically any place which is accessing that freed memory. Let's see how this will behave with his fix.

*** This bug has been marked as a duplicate of bug 706539 ***