goa-daemon crashed with SIGABRT in pthread_kill()

[Brooks Cameron Clemans]

Recently updated from 20.04->22.04->22.10 with 5.19.0-15-generic kernel on a Dell Precision 5570 Laptop. Many other failures like this have popped up. Not sure how to troubleshoot this one or what other information I can provide.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: gnome-online-accounts 3.46.0-1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
Date: Fri Oct 7 09:08:53 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ExecutablePath: /usr/libexec/goa-daemon
InstallationDate: Installed on 2022-08-30 (37 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
ProcCmdline: /usr/libexec/goa-daemon
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gnome-online-accounts
StacktraceTop:
 pthread_kill () at /lib/x86_64-linux-gnu/libc.so.6
 raise () at /lib/x86_64-linux-gnu/libc.so.6
 abort () at /lib/x86_64-linux-gnu/libc.so.6
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: goa-daemon crashed with SIGABRT in pthread_kill()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1990200, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.