Bug 1045281

Summary: [abrt] gnome-online-accounts: g_source_unref_internal(): goa-daemon killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
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: 22CC: bnocera, debarshir, edward.vonk, mmarzantowicz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/270304f49f2b6bc578e19cdffebe0df91ef1205e
Whiteboard: abrt_hash:2586850eb887404437a1c68f823136fa3a5a6b5e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:48:18 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
File: var_log_messages none

Description Adam Williamson 2013-12-20 04:30:44 UTC
Description of problem:
Didn't do anything specific, happens in the background or on start/shutdown.

Version-Release number of selected component:
gnome-online-accounts-3.11.2-1.fc21

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: g_source_unref_internal
executable:     /usr/libexec/goa-daemon
kernel:         3.13.0-0.rc3.git3.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 g_source_unref_internal at gmain.c:1994
 #1 g_source_iter_next at gmain.c:916
 #2 g_main_context_prepare at gmain.c:3316

Potential duplicate: bug 877922

Comment 1 Adam Williamson 2013-12-20 04:30:48 UTC
Created attachment 839347 [details]
File: backtrace

Comment 2 Adam Williamson 2013-12-20 04:30:49 UTC
Created attachment 839348 [details]
File: cgroup

Comment 3 Adam Williamson 2013-12-20 04:30:51 UTC
Created attachment 839349 [details]
File: core_backtrace

Comment 4 Adam Williamson 2013-12-20 04:30:52 UTC
Created attachment 839350 [details]
File: dso_list

Comment 5 Adam Williamson 2013-12-20 04:30:54 UTC
Created attachment 839351 [details]
File: environ

Comment 6 Adam Williamson 2013-12-20 04:30:55 UTC
Created attachment 839352 [details]
File: limits

Comment 7 Adam Williamson 2013-12-20 04:30:56 UTC
Created attachment 839353 [details]
File: maps

Comment 8 Adam Williamson 2013-12-20 04:30:58 UTC
Created attachment 839354 [details]
File: open_fds

Comment 9 Adam Williamson 2013-12-20 04:30:59 UTC
Created attachment 839355 [details]
File: proc_pid_status

Comment 10 Adam Williamson 2013-12-20 04:31:00 UTC
Created attachment 839356 [details]
File: var_log_messages

Comment 11 Mateusz Marzantowicz 2014-01-26 22:30:29 UTC
I confirm, this bug exists on F20

$ rpm -qa gnome-shell
gnome-shell-3.10.3-2.fc20.x86_64

Comment 12 Debarshi Ray 2014-03-18 16:18:42 UTC
*** Bug 1061675 has been marked as a duplicate of this bug. ***

Comment 13 Jaroslav Reznik 2015-03-03 15:20:31 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 14 Fedora End Of Life 2016-07-19 10:48:18 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.