[Evolution] evolution-calendar-factory (3.36.5) crash - backtrace included



Hi,

I am using evolution 3.36.5 (Ubuntu Focal) and the calendar backend
crashed with that backtrace:


#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:65
#1  0x00007f588503d210 in calc_ntlmv2_response (nt_hash_sz=..., lm_resp_sz=..., nt_resp_sz=..., nt_resp=..., 
lm_resp=..., target_info_sz=..., target_info=..., nonce=..., nt_hash=..., domain=..., user=...)
    at ../libsoup/soup-auth-ntlm.c:961
#2  soup_ntlm_response (host=..., target_info_sz=..., target_info=..., negotiate_target=..., 
ntlmv2_session=..., domain=..., lm_hash=..., nt_hash=..., user=..., nonce=...) at 
../libsoup/soup-auth-ntlm.c:961
#3  soup_auth_ntlm_get_connection_authorization (auth=..., msg=..., state=...) at 
../libsoup/soup-auth-ntlm.c:531
#4  0x00007f5885040aa4 in update_authorization_header (msg=msg@entry=..., auth=auth@entry=..., 
is_proxy=is_proxy@entry=...) at ../libsoup/soup-auth-manager.c:455
#5  0x00007f5885041aee in auth_msg_starting (msg=..., manager=...) at ../libsoup/soup-auth-manager.c:751
#9  0x00007f58856270f3 in <emit signal ??? on instance 0x7f57bc005f60 [ESoapMessage]> (instance=..., 
signal_id=..., detail=detail@entry=...) at ../../../gobject/gsignal.c:3555
    #6  0x00007f5885607802 in g_closure_invoke (closure=..., return_value=..., n_param_values=..., 
param_values=..., invocation_hint=...) at ../../../gobject/gclosure.c:810
    #7  0x00007f588561b814 in signal_emit_unlocked_R (node=node@entry=..., detail=detail@entry=..., 
instance=instance@entry=..., emission_return=emission_return@entry=..., 
instance_and_params=instance_and_params@entry=...)
    at ../../../gobject/gsignal.c:3743
    #8  0x00007f5885626bbe in g_signal_emit_valist (instance=..., signal_id=..., detail=..., 
var_args=var_args@entry=...) at ../../../gobject/gsignal.c:3499
#10 0x00007f588505a053 in soup_message_starting (msg=...) at ../libsoup/soup-message.c:1210
#11 0x00007f588506b468 in soup_session_send_queue_item (session=session@entry=..., item=item@entry=..., 
completion_cb=completion_cb@entry=...) at ../libsoup/soup-session.c:1337
#12 0x00007f58850706ec in soup_session_process_queue_item (loop=..., should_cleanup=..., item=..., 
session=...) at ../libsoup/soup-session.c:2006
#13 soup_session_process_queue_item (session=..., item=..., should_cleanup=..., loop=...) at 
../libsoup/soup-session.c:1965
#14 0x00007f5885070c12 in soup_session_real_send_message (session=..., msg=...) at 
../libsoup/soup-session.c:2237
#15 0x00007f587ac9aa97 in e_ews_notification_subscribe_folder_sync (notification=..., folders=..., 
subscription_id=subscription_id@entry=..., cancellable=...) at ./src/server/e-ews-notification.c:387
#16 0x00007f587ac9b228 in e_ews_notification_get_events_thread (user_data=...) at 
./src/server/e-ews-notification.c:936
#17 0x00007f5885545ad1 in g_thread_proxy (data=...) at ../../../glib/gthread.c:807
#18 0x00007f5884ca2609 in start_thread (arg=...) at pthread_create.c:477
#19 0x00007f5885259293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Seems like libsoup is the culprit here but I had no look at the sources
- anyone an idea what went wrong here and how to prevent that?

kind regards

Torsten

Attachment: smime.p7s
Description: S/MIME cryptographic signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]