Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1099115

Summary: [abrt] gnome-online-accounts: g_source_unref_internal(): goa-daemon killed by SIGSEGV
Product: Red Hat Enterprise Linux 7 Reporter: Jeff Bastian <jbastian>
Component: gnome-online-accountsAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: ayadav, debarshir, dkochuka, jwright, mcepl, pcfe, rstrode, vhumpa
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2586850eb887404437a1c68f823136fa3a5a6b5e
Fixed In Version: gnome-online-accounts-3.8.5-14.el7 Doc Type: Bug Fix
Doc Text:
Cause: Memory errors caused by races in threaded code Consequence: /usr/libexec/goa-daemon would crash if you were using Kerberos Fix: Fix the races and split out the Kerberos code into a separate process so that it does not affect the main daemon. Result: The daemon does not crash and is now more resilient against this class of bugs.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 09:08:04 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: sosreport.tar.xz none

Description Jeff Bastian 2014-05-19 13:59:55 UTC
Description of problem:
I woke my laptop from sleeping and gnome-online-accounts crashed.  I'm running KDE.

Version-Release number of selected component:
gnome-online-accounts-3.8.5-8.el7.1

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_source_unref_internal
executable:     /usr/libexec/goa-daemon
kernel:         3.10.0-122.el7.x86_64
runlevel:       unknown
type:           CCpp
uid:            12257

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_source_unref_internal at /lib64/libglib-2.0.so.0
 #1 g_source_iter_next at /lib64/libglib-2.0.so.0
 #2 g_main_context_prepare at /lib64/libglib-2.0.so.0
 #3 g_main_context_iterate.isra.22 at /lib64/libglib-2.0.so.0

Comment 1 Jeff Bastian 2014-05-19 13:59:58 UTC
Created attachment 897161 [details]
File: backtrace

Comment 2 Jeff Bastian 2014-05-19 13:59:59 UTC
Created attachment 897162 [details]
File: cgroup

Comment 3 Jeff Bastian 2014-05-19 14:00:01 UTC
Created attachment 897163 [details]
File: core_backtrace

Comment 4 Jeff Bastian 2014-05-19 14:00:03 UTC
Created attachment 897164 [details]
File: dso_list

Comment 5 Jeff Bastian 2014-05-19 14:00:08 UTC
Created attachment 897165 [details]
File: environ

Comment 6 Jeff Bastian 2014-05-19 14:00:10 UTC
Created attachment 897166 [details]
File: exploitable

Comment 7 Jeff Bastian 2014-05-19 14:00:12 UTC
Created attachment 897167 [details]
File: limits

Comment 8 Jeff Bastian 2014-05-19 14:00:15 UTC
Created attachment 897168 [details]
File: maps

Comment 9 Jeff Bastian 2014-05-19 14:00:17 UTC
Created attachment 897169 [details]
File: open_fds

Comment 10 Jeff Bastian 2014-05-19 14:00:20 UTC
Created attachment 897170 [details]
File: proc_pid_status

Comment 11 Jeff Bastian 2014-05-19 14:00:22 UTC
Created attachment 897171 [details]
File: var_log_messages

Comment 12 Jeff Bastian 2014-05-19 14:01:19 UTC
Created attachment 897172 [details]
File: sosreport.tar.xz

Comment 23 Matěj Cepl 2014-11-19 20:23:55 UTC
nothing has crashed on me during the manual testing and no reproducer available.

Comment 24 Patrick C. F. Ernzer 2015-02-03 10:31:27 UTC
Another user experienced a similar problem:

I have no idea why goa-daemon would be running seeing that I am under KDE.

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_source_unref_internal
executable:     /usr/libexec/goa-daemon
kernel:         3.10.0-123.13.2.el7.x86_64
package:        gnome-online-accounts-3.8.5-9.el7_0.1
reason:         goa-daemon killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            5037

Comment 26 errata-xmlrpc 2015-03-05 09:08:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0391.html