Description of problem: Random crash. Version-Release number of selected component: gnome-online-accounts-3.9.91-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/libexec/goa-daemon crash_function: magazine_chain_pop_head executable: /usr/libexec/goa-daemon kernel: 3.11.1-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:541 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_slist_prepend at gslist.c:267 #4 g_object_notify_queue_add at gobject.c:307 #5 object_set_property at gobject.c:1371 #6 g_object_new_internal at gobject.c:1779 #7 g_object_new_valist at gobject.c:2002 #9 g_socket_address_new_from_native at gsocketaddress.c:259 #10 do_lookup_by_name at gthreadedresolver.c:92 Potential duplicate: bug 951829
Created attachment 799666 [details] File: backtrace
Created attachment 799667 [details] File: cgroup
Created attachment 799668 [details] File: core_backtrace
Created attachment 799669 [details] File: dso_list
Created attachment 799670 [details] File: environ
Created attachment 799671 [details] File: exploitable
Created attachment 799672 [details] File: limits
Created attachment 799673 [details] File: maps
Created attachment 799674 [details] File: open_fds
Created attachment 799675 [details] File: proc_pid_status
Just pops up after a fresh install of F20. I added 3 accounts through the initial wizard (google, exchange, and facebook) and shortly thereafter aver 10 minutes or so this error is thrown reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/libexec/goa-daemon crash_function: magazine_chain_pop_head executable: /usr/libexec/goa-daemon kernel: 3.11.10-301.fc20.x86_64 package: gnome-online-accounts-3.10.2-1.fc20 reason: Process /usr/libexec/goa-daemon was killed by signal 11 (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.