Bug 1246707

Summary: [abrt] evolution-data-server: gdata_service_update_entry(): evolution-calendar-factory-subprocess killed by SIGABRT
Product: [Fedora] Fedora Reporter: Torsten Scholak <torsten.scholak>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mbarnes, mcrha, philip, torsten.scholak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/79de32492443214eb236f58157fa280b383f178b
Whiteboard: abrt_hash:4876edc4db61479d247270653159308f7a1b6183
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-30 04:40:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: core.5416 none

Description Torsten Scholak 2015-07-25 00:38:10 UTC 
Version-Release number of selected component:
evolution-data-server-3.17.4-1.fc24

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory-subprocess --factory gtasks --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2714x5 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2714/5
crash_function: gdata_service_update_entry
executable:     /usr/libexec/evolution-calendar-factory-subprocess
global_pid:     4364
kernel:         4.2.0-0.rc3.git3.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            10001

Truncated backtrace:
Thread no. 1 (6 frames)
 #4 gdata_service_update_entry at gdata/gdata-service.c:1661
 #5 gdata_tasks_service_update_task at gdata/services/tasks/gdata-tasks-service.c:781
 #6 ecb_gtasks_modify_objects at e-cal-backend-gtasks.c:1106
 #7 cal_backend_modify_objects_thread at e-cal-backend.c:2728
 #8 cal_backend_dispatch_thread at e-cal-backend.c:241
 #10 g_thread_proxy at gthread.c:764
Comment 1 Torsten Scholak 2015-07-25 00:38:12 UTC 
Created attachment 1055903 [details]
File: backtrace
Comment 2 Torsten Scholak 2015-07-25 00:38:13 UTC 
Created attachment 1055904 [details]
File: cgroup
Comment 3 Torsten Scholak 2015-07-25 00:38:14 UTC 
Created attachment 1055905 [details]
File: core_backtrace
Comment 4 Torsten Scholak 2015-07-25 00:38:15 UTC 
Created attachment 1055906 [details]
File: dso_list
Comment 5 Torsten Scholak 2015-07-25 00:38:16 UTC 
Created attachment 1055907 [details]
File: environ
Comment 6 Torsten Scholak 2015-07-25 00:38:16 UTC 
Created attachment 1055908 [details]
File: limits
Comment 7 Torsten Scholak 2015-07-25 00:38:18 UTC 
Created attachment 1055909 [details]
File: maps
Comment 8 Torsten Scholak 2015-07-25 00:38:18 UTC 
Created attachment 1055910 [details]
File: mountinfo
Comment 9 Torsten Scholak 2015-07-25 00:38:19 UTC 
Created attachment 1055911 [details]
File: namespaces
Comment 10 Torsten Scholak 2015-07-25 00:38:20 UTC 
Created attachment 1055912 [details]
File: open_fds
Comment 11 Torsten Scholak 2015-07-25 00:38:21 UTC 
Created attachment 1055913 [details]
File: proc_pid_status
Comment 12 Torsten Scholak 2015-07-25 00:38:36 UTC 
Created attachment 1055925 [details]
File: core.5416
Comment 13 Milan Crha 2015-07-27 06:46:26 UTC 
Thanks for a bug report. I see that the process crashed with the Google Tasks backend, something in the libgdata code. Did it happen only once, or you are able to reproduce this, please? I do not see much from the backtrace, thus asking. I guess this happened when an update on a task or when a new task entry was recognized, then the backend tried to update its local cache with the change/new task, but there was hit some assertion in the libgdata code which aborted the process.
Comment 14 Philip Withnall 2015-07-29 11:07:37 UTC 
Looks like an upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=753012

I am unlikely to have time to fix this for the next three weeks. :-(
Comment 15 Milan Crha 2015-07-30 04:40:32 UTC 
Thanks for the pointer. Let's deal with this upstream then, to avoid work duplication.