Hide Forgot
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
Created attachment 839293 [details] File: backtrace
Created attachment 839294 [details] File: cgroup
Created attachment 839295 [details] File: core_backtrace
Created attachment 839296 [details] File: dso_list
Created attachment 839297 [details] File: environ
Created attachment 839298 [details] File: exploitable
Created attachment 839299 [details] File: limits
Created attachment 839300 [details] File: maps
Created attachment 839301 [details] File: open_fds
Created attachment 839302 [details] File: proc_pid_status
Created attachment 839303 [details] File: var_log_messages
*** Bug 1045268 has been marked as a duplicate of this bug. ***
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).
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
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
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.
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.