My workaround above (calling "goa-daemon --replace" on login) isnt working all the time, sadly. On occasion, I am ending up with 3 or 4 instances of goa-daemon per user (I guess --replace isnt able to kill the previous instance?). Multiple instances results in high CPU usage.
I have also seen goa-daemon report that it cannot connect to the keychain: "/usr/lib/gnome-online-accounts/goa-daemon --replace goa-daemon-Message: goa-daemon version 3.24.0 starting (goa-daemon:18954): GoaBackend-WARNING **: secret_password_lookup_sync() returned NULL goa-daemon-Message: /org/gnome/OnlineAccounts/Accounts/account_1496262706_0: Setting AttentionNeeded to TRUE because EnsureCredentials() failed with: No credentials found in the keyring (goa-error-quark, 4)" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
