Bug 1026159

Summary: [abrt] gnome-online-accounts-3.10.1-2.fc20: g_thread_abort: Process /usr/libexec/goa-daemon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: gnome-online-accountsAssignee: Debarshi Ray <debarshir>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: b3n.poni, bnocera, debarshir, dwilliams, lray+redhatbugzilla, mael.lavault, mjs, pavkamlc, zman0900
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/35d432d3c4dccffe83253168ae0f6078f58c3baa
Whiteboard: abrt_hash:7d6a09fdc6da70cd993c234ba5b6c9b877b07a78
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 12:48:16 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Mikhail 2013-11-04 05:06:47 UTC
Version-Release number of selected component:
gnome-online-accounts-3.10.1-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_thread_abort
executable:     /usr/libexec/goa-daemon
kernel:         3.11.6-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_thread_abort at gthread-posix.c:79
 #3 g_mutex_lock at gthread-posix.c:214
 #4 g_source_destroy_internal at gmain.c:1189
 #5 g_source_destroy at gmain.c:1256
 #6 soup_session_dispose at soup-session.c:304
 #8 ews_client_autodiscover_data_free at goaewsclient.c:107

Potential duplicate: bug 928634

Comment 1 Mikhail 2013-11-04 05:06:55 UTC
Created attachment 818883 [details]
File: backtrace

Comment 2 Mikhail 2013-11-04 05:06:58 UTC
Created attachment 818884 [details]
File: cgroup

Comment 3 Mikhail 2013-11-04 05:07:02 UTC
Created attachment 818885 [details]
File: core_backtrace

Comment 4 Mikhail 2013-11-04 05:07:05 UTC
Created attachment 818886 [details]
File: dso_list

Comment 5 Mikhail 2013-11-04 05:07:08 UTC
Created attachment 818887 [details]
File: environ

Comment 6 Mikhail 2013-11-04 05:07:12 UTC
Created attachment 818888 [details]
File: limits

Comment 7 Mikhail 2013-11-04 05:07:15 UTC
Created attachment 818889 [details]
File: maps

Comment 8 Mikhail 2013-11-04 05:07:18 UTC
Created attachment 818890 [details]
File: open_fds

Comment 9 Mikhail 2013-11-04 05:07:22 UTC
Created attachment 818891 [details]
File: proc_pid_status

Comment 10 Dan Ziemba 2014-03-08 20:58:40 UTC
Another user experienced a similar problem:

Happens randomly while attempting to use Evolution with my exchange account (office 365).  

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_thread_abort
executable:     /usr/libexec/goa-daemon
kernel:         3.12.8-300.fc20.x86_64
package:        gnome-online-accounts-3.10.2-1.fc20
reason:         goa-daemon killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 11 Dan Ziemba 2014-03-08 21:01:18 UTC
This might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1031257.  Also happens with kernel 3.13.5 and g-o-a 3.10.2-1

Comment 12 Dave Williams 2014-03-11 01:59:44 UTC
Another user experienced a similar problem:

This happened while applications were loading right after login.

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_thread_abort
executable:     /usr/libexec/goa-daemon
kernel:         3.13.3-201.fc20.x86_64
package:        gnome-online-accounts-3.10.2-1.fc20
reason:         goa-daemon killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Fedora Admin XMLRPC Client 2015-01-28 09:15:16 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 14 Fedora End Of Life 2015-05-29 09:41:01 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 15 Fedora End Of Life 2015-06-29 12:48:16 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.