I found the bug described and confirmed on redhat, where I also found the solution. (although they have the goa-demon in the /usr/libexec/ folder) https://bugzilla.redhat.com/show_bug.cgi?id=1340203
As a work-around, for each user account I created a new file in ~/.config/autostart/ called goa-replace.desktop, and in a text-editor entered the following: [Desktop Entry] Name=GOA Replace Exec=/usr/lib/gnome-online-accounts/goa-daemon --replace NoDisplay=true Terminal=false Type=Application The problem seems to be that dbus is spawning goa-daemon, but then not killing the process when the user logs out. gnome-keyring IS killed, and this breaks the link between the two. Not sure what the *real* solution is, seems to be a big debate about how systemd leaves 'lingering' processes from users after log out. I see 28 processes left running after a user logs out. Surely this needs to be cleaned up??? Is there a better way to force systemd to properly close a users session? ** Bug watch added: Red Hat Bugzilla #1340203 https://bugzilla.redhat.com/show_bug.cgi?id=1340203 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
