Version-Release number of selected component: evolution-3.36.5-1.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-3.scope cmdline: /usr/bin/evolution crash_function: __memmove_avx_unaligned_erms executable: /usr/bin/evolution journald_cursor: s=79e04f71da034238bf8bb05bdacd91ff;i=8a73f0;b=c76456a2525f48c8b775544a1e601830;m=7cd9f26f16;t=5b087e0e59f8e;x=faff24e9c7f1ce87 kernel: 5.8.10-200.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memmove_avx_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:416 #1 memcpy at /usr/include/bits/string_fortified.h:34 #2 g_array_append_vals at ../glib/garray.c:481 #4 g_byte_array_append at ../glib/garray.c:2376 #5 ews_notification_soup_got_chunk at /usr/src/debug/evolution-ews-3.36.5-1.fc32.x86_64/src/server/e-ews-notification.c:738 #6 g_cclosure_marshal_VOID__BOXEDv at ../gobject/gmarshal.c:1686 #7 _g_closure_invoke_va at ../gobject/gclosure.c:873 #10 soup_message_got_chunk at ../libsoup/soup-message.c:1192 #11 io_read at ../libsoup/soup-message-io.c:770 #12 io_run_until at ../libsoup/soup-message-io.c:978
Created attachment 1717887 [details] File: backtrace
Created attachment 1717888 [details] File: core_backtrace
Created attachment 1717889 [details] File: cpuinfo
Created attachment 1717890 [details] File: dso_list
Created attachment 1717891 [details] File: environ
Created attachment 1717892 [details] File: exploitable
Created attachment 1717893 [details] File: limits
Created attachment 1717894 [details] File: maps
Created attachment 1717895 [details] File: mountinfo
Created attachment 1717896 [details] File: open_fds
Created attachment 1717897 [details] File: proc_pid_status
Created attachment 1717898 [details] File: xsession_errors
Thanks for a bug report. I see this crashed when reading a change notification from an Exchange server. Maybe this is related to bug #1842729, or any similar bug report. It was hard to reproduce, or better said, I've not been able to reproduce it (and debug it) myself yet.
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 ***