Bug 1840522

Summary: [abrt] evolution-data-server: xmlStrndup__internal_alias(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
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: 32CC: 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/ba85edda54fae1a0d6247417cec8e5be0f8e1ce5
Whiteboard: abrt_hash:565bb616b407e58779a19282c96fbb4f77923c68;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-26 13:40:37 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: 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 Jan Vlug 2020-05-27 06:34:29 UTC 
Version-Release number of selected component:
evolution-data-server-3.36.2-1.fc32

Additional info:
reporter:       libreport-2.13.1
backtrace_rating: 3
cgroup:         0::/user.slice/user-1000.slice/user/evolution-calendar-factory.service
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: xmlStrndup__internal_alias
executable:     /usr/libexec/evolution-calendar-factory
journald_cursor: s=bb3645216bd54966971abbb4ca53a0e0;i=9ad0;b=36b85bba2aa84b19a09142c5cb239f95;m=12a570985e;t=5a66181448a2c;x=68f5d4ad60e404c3
kernel:         5.6.12-300.fc32.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Jan Vlug 2020-05-27 06:34:33 UTC 
Created attachment 1692549 [details]
File: backtrace
Comment 2 Jan Vlug 2020-05-27 06:34:36 UTC 
Created attachment 1692550 [details]
File: core_backtrace
Comment 3 Jan Vlug 2020-05-27 06:34:37 UTC 
Created attachment 1692551 [details]
File: cpuinfo
Comment 4 Jan Vlug 2020-05-27 06:34:39 UTC 
Created attachment 1692552 [details]
File: dso_list
Comment 5 Jan Vlug 2020-05-27 06:34:40 UTC 
Created attachment 1692553 [details]
File: environ
Comment 6 Jan Vlug 2020-05-27 06:34:42 UTC 
Created attachment 1692554 [details]
File: exploitable
Comment 7 Jan Vlug 2020-05-27 06:34:44 UTC 
Created attachment 1692555 [details]
File: limits
Comment 8 Jan Vlug 2020-05-27 06:34:47 UTC 
Created attachment 1692556 [details]
File: maps
Comment 9 Jan Vlug 2020-05-27 06:34:48 UTC 
Created attachment 1692557 [details]
File: mountinfo
Comment 10 Jan Vlug 2020-05-27 06:34:50 UTC 
Created attachment 1692558 [details]
File: open_fds
Comment 11 Jan Vlug 2020-05-27 06:34:51 UTC 
Created attachment 1692559 [details]
File: proc_pid_status
Comment 12 Milan Crha 2020-05-28 07:42:09 UTC 
Thanks for a bug report. The place of the crash is somehow odd. Do you have any reproducer for this, please? Maybe it's a variant of bug #1823240, as it involves e_ews_notification_subscribe_folder_sync(), though the overall circumstances do not seem to be replicated here.
Comment 13 Milan Crha 2021-01-26 13:40:37 UTC 
I believe this is a similar cause as bug #1818995, thus I mark this as a duplicate of it.

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