Bug 1380846

Summary: [abrt] evolution-data-server: soup_session_feature_add_feature(): evolution-calendar-factory-subprocess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: David Novák <novak.david>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/80c09dbc69e9ae3bcc55f0d79edf00ce6209ecd4
Whiteboard: abrt_hash:2f6f9daef98dd2156865baeab098d973f0263e16;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:16:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description David Novák 2016-09-30 18:41:05 UTC
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

Comment 1 David Novák 2016-09-30 18:41:10 UTC
Created attachment 1206336 [details]
File: backtrace

Comment 2 David Novák 2016-09-30 18:41:12 UTC
Created attachment 1206337 [details]
File: cgroup

Comment 3 David Novák 2016-09-30 18:41:13 UTC
Created attachment 1206338 [details]
File: core_backtrace

Comment 4 David Novák 2016-09-30 18:41:15 UTC
Created attachment 1206339 [details]
File: dso_list

Comment 5 David Novák 2016-09-30 18:41:16 UTC
Created attachment 1206340 [details]
File: environ

Comment 6 David Novák 2016-09-30 18:41:18 UTC
Created attachment 1206341 [details]
File: exploitable

Comment 7 David Novák 2016-09-30 18:41:19 UTC
Created attachment 1206342 [details]
File: limits

Comment 8 David Novák 2016-09-30 18:41:21 UTC
Created attachment 1206343 [details]
File: maps

Comment 9 David Novák 2016-09-30 18:41:22 UTC
Created attachment 1206344 [details]
File: mountinfo

Comment 10 David Novák 2016-09-30 18:41:24 UTC
Created attachment 1206345 [details]
File: namespaces

Comment 11 David Novák 2016-09-30 18:41:25 UTC
Created attachment 1206346 [details]
File: open_fds

Comment 12 David Novák 2016-09-30 18:41:27 UTC
Created attachment 1206347 [details]
File: proc_pid_status

Comment 13 David Novák 2016-09-30 18:41:29 UTC
Created attachment 1206348 [details]
File: var_log_messages

Comment 14 Milan Crha 2016-10-05 11:08:48 UTC
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?

Comment 15 David Novák 2016-10-05 18:41:18 UTC
(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.

Comment 16 Fedora End Of Life 2017-07-25 23:18:13 UTC
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.

Comment 17 Fedora End Of Life 2017-08-08 19:16:40 UTC
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.