After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756277 - After upgrade to GNOME 3.18, GOA always returns timeouts
After upgrade to GNOME 3.18, GOA always returns timeouts
Status: RESOLVED DUPLICATE of bug 751524
Product: gnome-online-accounts
Classification: Core
Component: general
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Online Accounts maintainer(s)
GNOME Online Accounts maintainer(s)
https://bugs.archlinux.org/task/46626
Depends on:
Blocks:
 
 
Reported: 2015-10-09 08:56 UTC by Johannes Rohr
Modified: 2015-11-25 18:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Johannes Rohr 2015-10-09 08:56:33 UTC
I am on Arch Linux and today upgraded GNOME to 3.18. 

Unfortunately anything relying on GOA seems to be messed up now. The Google accounts were shown as expired, however, re-authenticating didn't help, instead I had to re-add the account. Now empathy fails to authenticate with Google talk, Google drive support in Nautilus does nothing (first I get "Operation already pending", and then a timeout alert), also my owncloud share appears in Nautilus but cannot be mounted, for the same reason (I see goa timout messages in Syslog), while mounting it manually via a WebDAV URI works flawlessly. 

This is what I see when I try to get empathy to re-logon with google chat: 
Okt 09 10:49:51 tommy dbus-daemon[3925]: Activating service name='org.freedesktop.Telepathy.Client.Empathy.Auth'
Okt 09 10:49:51 tommy dbus-daemon[3925]: Successfully activated service 'org.freedesktop.Telepathy.Client.Empathy.Auth'
Okt 09 10:51:15 tommy org.gnome.OnlineAccounts[3925]: (goa-daemon:4057): GoaBackend-WARNING **: secret_password_lookup_sync() returned NULL
In Evolution ALL calendars except for readonly ICS subscriptions have disappeared.

To in total, it's a complete mess. 

With other users on the same computer the situation is somewhat better, but varied. I have tried to re-authenticate several times, and according to g-o-a everything is fine, but still it's completely dysfunctional.
Comment 1 Johannes Rohr 2015-10-09 19:38:32 UTC
Now submitted as a but in Arch Linux https://bugs.archlinux.org/task/46626
Comment 2 Debarshi Ray 2015-11-25 18:52:33 UTC

*** This bug has been marked as a duplicate of bug 751524 ***