Red Hat Bugzilla – Bug 1247195
[abrt] evolution-data-server: send_propfind(): evolution-addressbook-factory-subprocess killed by SIGSEGV
Last modified: 2015-07-30 00:37:33 EDT
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-addressbook-factory-subprocess --factory webdav --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx2629x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/2629/2
runlevel: N 5
Thread no. 1 (7 frames)
#0 send_propfind at e-book-backend-webdav.c:583
#1 book_backend_webdav_test_can_connect at e-book-backend-webdav.c:1223
#2 book_backend_webdav_authenticate_sync at e-book-backend-webdav.c:1851
#3 e_backend_authenticate_sync at e-backend.c:239
#4 backend_source_authenticate_thread at e-backend.c:300
#5 g_thread_proxy at gthread.c:764
#7 __libc_ifunc_impl_list at ../sysdeps/x86_64/multiarch/ifunc-impl-list.c:96
Created attachment 1056594 [details]
Created attachment 1056595 [details]
Created attachment 1056596 [details]
Created attachment 1056597 [details]
Created attachment 1056598 [details]
Created attachment 1056599 [details]
Created attachment 1056600 [details]
Created attachment 1056601 [details]
Created attachment 1056602 [details]
Created attachment 1056603 [details]
Created attachment 1056604 [details]
Thanks for a bug report. It looks like the URL for one of your WebDAV address books is incorrect. Could you verify that all your WebDAV address books have configured correct URL, please?
I just found an older bug report about the same, thus I mark this as a duplicate of it. I'm still interested in the answer for the above question.
*** This bug has been marked as a duplicate of bug 1051863 ***
All is ok.
Then it might be something else. I committed a change upstream which will report an error with the broken URL, instead of crashing the application (unless there's a use-after-free involved, which would be unfortunate), thus it might get slightly better than it is now.
Seems fine. Could it have been that the server was down while Evolution tried to sync?
I do not think so. The crash happened due to an incorrect URL being used when creating a SoupMessage structure, but it wasn't checked whether the returned pointer is valid and it was dereferenced, which with NULL means a crash. This all is done completely locally.