Bug 1045241

Summary: [abrt] gnome-online-accounts: __pthread_mutex_lock(): 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: 20CC: admiller, akurtako, bnocera, bpk678, braden, debarshir, dmaley, dvacek, emcnabb, jesse.brandeburg, kubrick, mmilata, mwesley, plarsen, pmutha, sjenning, tcarlin, thenscheid, valtri
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b01d7b1922702a8b23c7b1c1dbeaff2b3ec30d59
Whiteboard: abrt_hash:0020b303fc7fe81ccd0078067585c7f38c860753
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:38:51 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Adam Williamson 2013-12-20 01:21:16 UTC
Description of problem:
Didn't do anything specific to trigger this, happened on startup or shutdown I believe.

Version-Release number of selected component:
gnome-online-accounts-3.10.2-1.fc20

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66
 #1 g_mutex_lock at gthread-posix.c:213
 #2 g_source_ref at gmain.c:1952
 #3 on_cancelled at goaalarm.c:259
 #4 _g_closure_invoke_va at gclosure.c:840
 #7 g_cancellable_cancel at gcancellable.c:503
 #8 goa_alarm_set_time at goaalarm.c:595
 #9 set_alarm at goakerberosidentity.c:789
 #10 reset_alarms at goakerberosidentity.c:875
 #11 goa_kerberos_identity_update at goakerberosidentity.c:1310

Comment 1 Adam Williamson 2013-12-20 01:21:20 UTC
Created attachment 839293 [details]
File: backtrace

Comment 2 Adam Williamson 2013-12-20 01:21:23 UTC
Created attachment 839294 [details]
File: cgroup

Comment 3 Adam Williamson 2013-12-20 01:21:25 UTC
Created attachment 839295 [details]
File: core_backtrace

Comment 4 Adam Williamson 2013-12-20 01:21:26 UTC
Created attachment 839296 [details]
File: dso_list

Comment 5 Adam Williamson 2013-12-20 01:21:28 UTC
Created attachment 839297 [details]
File: environ

Comment 6 Adam Williamson 2013-12-20 01:21:29 UTC
Created attachment 839298 [details]
File: exploitable

Comment 7 Adam Williamson 2013-12-20 01:21:30 UTC
Created attachment 839299 [details]
File: limits

Comment 8 Adam Williamson 2013-12-20 01:21:32 UTC
Created attachment 839300 [details]
File: maps

Comment 9 Adam Williamson 2013-12-20 01:21:35 UTC
Created attachment 839301 [details]
File: open_fds

Comment 10 Adam Williamson 2013-12-20 01:21:37 UTC
Created attachment 839302 [details]
File: proc_pid_status

Comment 11 Adam Williamson 2013-12-20 01:21:40 UTC
Created attachment 839303 [details]
File: var_log_messages

Comment 12 Debarshi Ray 2014-04-10 09:04:15 UTC
*** Bug 1045268 has been marked as a duplicate of this bug. ***

Comment 13 kubrick@fgv6.net 2014-07-31 12:32:41 UTC
This is still happening by the way.
Today it got triggered either by me authenticating with kinit or immediately after when the deja-dup backup started (is backs up on a remote volume using kerberos authentication).

Comment 14 Marty Wesley 2014-10-08 15:11:28 UTC
Another user experienced a similar problem:

I don't know what caused the problem. The crash happened while I was away from my computer.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: __pthread_mutex_lock
executable:     /usr/libexec/goa-daemon
kernel:         3.16.3-200.fc20.x86_64
package:        gnome-online-accounts-3.10.5-1.fc20
reason:         goa-daemon killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            2774

Comment 15 Peter Larsen 2014-10-14 19:35:05 UTC
Another user experienced a similar problem:

All online accounts are disabled since they don't seem to work. Did a reboot and this error was there on startup. Not sure what caused it directly.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: __pthread_mutex_lock
executable:     /usr/libexec/goa-daemon
kernel:         3.16.4-200.fc20.x86_64
package:        gnome-online-accounts-3.10.5-1.fc20
reason:         goa-daemon killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

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

Comment 17 Fedora End Of Life 2015-05-29 10:04: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 18 Fedora End Of Life 2015-06-29 13:38:51 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.