Version-Release number of selected component: evolution-data-server-3.12.1-2.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: socket_connect_finish executable: /usr/libexec/evolution-calendar-factory kernel: 3.15.0-0.rc1.git2.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 socket_connect_finish at /lib64/libsoup-2.4.so.1 #1 soup_connection_connect_sync at /lib64/libsoup-2.4.so.1 #2 soup_session_process_queue_item at /lib64/libsoup-2.4.so.1 #3 soup_session_real_send_message at /lib64/libsoup-2.4.so.1 #4 send_and_handle_redirection at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so #5 caldav_server_list_objects at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so #6 synchronize_cache at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so #7 caldav_synch_slave_loop at /usr/lib64/evolution-data-server/calendar-backends/libecalbackendcaldav.so #8 g_thread_proxy at /lib64/libglib-2.0.so.0
Created attachment 891436 [details] File: backtrace
Created attachment 891437 [details] File: cgroup
Created attachment 891438 [details] File: core_backtrace
Created attachment 891439 [details] File: dso_list
Created attachment 891440 [details] File: environ
Created attachment 891441 [details] File: exploitable
Created attachment 891442 [details] File: limits
Created attachment 891443 [details] File: maps
Created attachment 891444 [details] File: open_fds
Created attachment 891445 [details] File: proc_pid_status
Created attachment 891446 [details] File: var_log_messages
Dan, do you have any idea what this can be about, please? The libsoup usage code in CalDAV is pretty straightforward, though, if I'm not mistaken, then multiple threads can access the soup session, one is the synchronize thread another is the one which calls soup_session_abort(). Can that be (part of) the problem?
Hm... yeah, soup_socket_connect_sync_internal() doesn't hold a ref on the socket, so if another thread destroyed it while it was connecting, *boom*. Should be an easy fix.
fixed upstream, will make it into rawhide with the GNOME 3.13.2 release in a bit over a week
Thanks. I'm moving this bug report to libsoup, as there was done the fix.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.