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
Created attachment 1692549 [details] File: backtrace
Created attachment 1692550 [details] File: core_backtrace
Created attachment 1692551 [details] File: cpuinfo
Created attachment 1692552 [details] File: dso_list
Created attachment 1692553 [details] File: environ
Created attachment 1692554 [details] File: exploitable
Created attachment 1692555 [details] File: limits
Created attachment 1692556 [details] File: maps
Created attachment 1692557 [details] File: mountinfo
Created attachment 1692558 [details] File: open_fds
Created attachment 1692559 [details] File: proc_pid_status
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.
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 ***