*** This bug is a duplicate of bug 1610944 ***
https://bugs.launchpad.net/bugs/1610944
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1610944, so it 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. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 1610944
GNOME Online Accounts breaks if you log out (until you reboot)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1695775
Title:
goa-daemon not stopped on logout, and gnome-keyring unusable on next
log in
Status in gnome-online-accounts package in Ubuntu:
New
Bug description:
Bug seen in Evolution - fails to connect to my google accounts on
second log-in. Accounts are set up fine, but after a log out then log
back in, they fail.
Error reported in Evolution is:
"Failed to authenticate: Failed to obtain an access token for
'------@gmail.com':Failed to retrieve credentials from the keyring"
It is fixed by running "/usr/lib/gnome-online-accounts/goa-daemon
--replace" in the terminal.
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?
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-online-accounts 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jun 4 21:48:59 2017
InstallationDate: Installed on 2017-05-03 (32 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1695775/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
