Bug 1728629

Summary: [abrt] evolution-data-server: ews_notification_soup_got_chunk(): evolution-addressbook-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Thomas Lake <tom>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: caillon+fedoraproject, john.j5live, mcrha, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0cc41e511c79fed3899f2cf64ef73c55651b9171
Whiteboard: abrt_hash:58ed101bac39e5f60c52a067f1b239b0c5169e84;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-10 13:16:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Thomas Lake 2019-07-10 10:21:55 UTC
Version-Release number of selected component:
evolution-data-server-3.32.3-1.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-addressbook-factory
crash_function: ews_notification_soup_got_chunk
executable:     /usr/libexec/evolution-addressbook-factory
journald_cursor: s=822aee42f78a4bddba3716873c08e226;i=2c107;b=f82560fed9a44432958aabd0ffa1926b;m=117461d97;t=58d50dd075f53;x=c7c5a5fe12c6d3cb
kernel:         5.1.16-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ews_notification_soup_got_chunk at /usr/src/debug/evolution-ews-3.32.2-1.fc30.x86_64/src/server/e-ews-notification.c:698
 #1 g_cclosure_marshal_VOID__BOXEDv at ../gobject/gmarshal.c:1686
 #2 _g_closure_invoke_va at ../gobject/gclosure.c:873
 #5 soup_message_got_chunk at ../libsoup/soup-message.c:1132
 #6 io_read at ../libsoup/soup-message-io.c:774
 #7 io_run_until at ../libsoup/soup-message-io.c:986
 #8 io_run at ../libsoup/soup-message-io.c:1057
 #9 soup_message_io_client at ../libsoup/soup-message-io.c:1237
 #10 soup_message_send_request at ../libsoup/soup-message-client-io.c:161
 #11 soup_connection_send_request at ../libsoup/soup-connection.c:753

Potential duplicate: bug 1672791

Comment 1 Thomas Lake 2019-07-10 10:21:59 UTC
Created attachment 1589054 [details]
File: backtrace

Comment 2 Thomas Lake 2019-07-10 10:22:00 UTC
Created attachment 1589055 [details]
File: cgroup

Comment 3 Thomas Lake 2019-07-10 10:22:01 UTC
Created attachment 1589056 [details]
File: core_backtrace

Comment 4 Thomas Lake 2019-07-10 10:22:02 UTC
Created attachment 1589057 [details]
File: cpuinfo

Comment 5 Thomas Lake 2019-07-10 10:22:04 UTC
Created attachment 1589058 [details]
File: dso_list

Comment 6 Thomas Lake 2019-07-10 10:22:05 UTC
Created attachment 1589059 [details]
File: environ

Comment 7 Thomas Lake 2019-07-10 10:22:06 UTC
Created attachment 1589060 [details]
File: exploitable

Comment 8 Thomas Lake 2019-07-10 10:22:07 UTC
Created attachment 1589061 [details]
File: limits

Comment 9 Thomas Lake 2019-07-10 10:22:09 UTC
Created attachment 1589062 [details]
File: maps

Comment 10 Thomas Lake 2019-07-10 10:22:10 UTC
Created attachment 1589063 [details]
File: mountinfo

Comment 11 Thomas Lake 2019-07-10 10:22:12 UTC
Created attachment 1589064 [details]
File: open_fds

Comment 12 Thomas Lake 2019-07-10 10:22:13 UTC
Created attachment 1589065 [details]
File: proc_pid_status

Comment 13 Milan Crha 2019-07-10 13:16:15 UTC
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

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