Hide Forgot
Version-Release number of selected component: evolution-data-server-3.20.5-4.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory caldav --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx1614x5 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/1614/5 crash_function: soup_session_feature_add_feature executable: /usr/libexec/evolution-calendar-factory-subprocess global_pid: 7958 kernel: 4.7.4-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 soup_session_feature_add_feature at soup-session-feature.c:173 #1 caldav_maybe_prepare_bearer_auth at e-cal-backend-caldav.c:396 #2 open_calendar_wrapper at e-cal-backend-caldav.c:2981 #3 caldav_authenticate_sync at e-cal-backend-caldav.c:5504 #4 e_backend_authenticate_sync at e-backend.c:248 #5 backend_source_authenticate_thread at e-backend.c:309 #6 g_thread_proxy at gthread.c:780
Created attachment 1206336 [details] File: backtrace
Created attachment 1206337 [details] File: cgroup
Created attachment 1206338 [details] File: core_backtrace
Created attachment 1206339 [details] File: dso_list
Created attachment 1206340 [details] File: environ
Created attachment 1206341 [details] File: exploitable
Created attachment 1206342 [details] File: limits
Created attachment 1206343 [details] File: maps
Created attachment 1206344 [details] File: mountinfo
Created attachment 1206345 [details] File: namespaces
Created attachment 1206346 [details] File: open_fds
Created attachment 1206347 [details] File: proc_pid_status
Created attachment 1206348 [details] File: var_log_messages
Thanks for a bug report. I see from the backtrace that this happened when one of your CalDAV calendars (possibly a Google calendar, either configured by GNOME Online Accounts or directly in the Evolution) was authenticating with the server. The backtrace suggests that this crashed when the calendar disconnected from the server, while, at the same time, it was authenticating to it. Might there be some connection disruption involved in the time of the crash?
(In reply to Milan Crha from comment #14) > Thanks for a bug report. I see from the backtrace that this happened when > one of your CalDAV calendars (possibly a Google calendar, either configured > by GNOME Online Accounts or directly in the Evolution) was authenticating > with the server. The backtrace suggests that this crashed when the calendar > disconnected from the server, while, at the same time, it was authenticating > to it. Might there be some connection disruption involved in the time of the > crash? No, there were no problems with connection when it happened (or maybe it was very short, so I didn't notice). It seemed to simply crash. And yes, it's Google Calendar configured through GOA.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.