Version-Release number of selected component: evolution-data-server-3.22.3-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory ews --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2433x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2433/3 crash_function: xmlFindCharEncodingHandler__internal_alias executable: /usr/libexec/evolution-addressbook-factory-subprocess global_pid: 4104 kernel: 4.8.15-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 xmlFindCharEncodingHandler__internal_alias at encoding.c:1670 #1 xmlDocDumpFormatMemoryEnc__internal_alias at xmlsave.c:2443 #2 xmlDocDumpMemory__internal_alias at xmlsave.c:2496 #3 e_soap_message_persist at e-soap-message.c:1088 #4 e_ews_message_write_footer at e-ews-message.c:270 #5 e_ews_connection_get_folder at e-ews-connection.c:5864 #6 e_ews_connection_get_folder_sync at e-ews-connection.c:5929 #7 e_ews_connection_try_credentials_sync at e-ews-connection.c:2262 #8 e_book_backend_ews_authenticate_sync at e-book-backend-ews.c:4263 #9 e_backend_authenticate_sync at e-backend.c:248 Potential duplicate: bug 1380268
Created attachment 1239558 [details] File: backtrace
Created attachment 1239559 [details] File: cgroup
Created attachment 1239560 [details] File: core_backtrace
Created attachment 1239561 [details] File: dso_list
Created attachment 1239562 [details] File: environ
Created attachment 1239563 [details] File: exploitable
Created attachment 1239564 [details] File: limits
Created attachment 1239565 [details] File: maps
Created attachment 1239566 [details] File: mountinfo
Thanks for a bug report. This seems to be the same as bug #1380268, thus I mark this as a duplicate of it. There is missing a reproducer, unfortunately, thus if you'd have any steps which would help to reproduce the crash, then it'll be appreciated. *** This bug has been marked as a duplicate of bug 1380268 ***
Hi, unfortunately I still don't have a way to reproduce... I'll let you know if I find a way!
Thanks for the update and for following the bug. That's no problem you cannot reproduce, I suspect the bug itself depends on some current state of the machine and/or data and finding which it is, and also reproduce certain timing, is not that easy. I can be wrong with my assumptions, though.