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 772768 - Accounts fail to connect to Google - authentication times out...
Accounts fail to connect to Google - authentication times out...
Status: RESOLVED DUPLICATE of bug 764029
Product: gnome-online-accounts
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Online Accounts maintainer(s)
GNOME Online Accounts maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-10-11 16:11 UTC by piedro.kulman
Modified: 2017-06-07 16:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description piedro.kulman 2016-10-11 16:11:25 UTC
The online accounts do not connect to Google anymore. 

"can't get access token" ... timeout... 

I could create a new Goolge account but evolution couldn't connect to it. 

GOA has given no indication of failure... I guess here are a few things: 

- Google tokens cannot be retrieved by evolution/GOA 
- GOA should indicate if an added account doesn't work or fails to connect with the services chosen in the right panel 
- there should be a way to edit the accounts in GOA once added otherwise setting them up after every failure will produce lots of reconfiguration in evolution 

BTW, this seems to only affect GOA, Kamil or thunderbird do not have the same problem... now this may be naive but it's all opensource, isn't it, so maybe the best fix would be to look at their code and do it this way? 

As is evolution can't access anything Google related anymore. 

thx for reading, p.
Comment 1 André Klapper 2016-10-12 19:20:35 UTC
Does the problem still occur after "/usr/libexec/goa-daemon --replace"?
Comment 2 piedro.kulman 2016-10-14 16:28:27 UTC
AFter updating to the latest 3.22 in ARch repositories I have not had this problem after reboot. Maybe it comes back after a few ours - I o not know yet... 

I'll post back. 

ty,p.
Comment 3 piedro.kulman 2016-11-09 13:17:55 UTC
/usr/libexec/goa-daemon --replace 

>> command not found
Comment 4 André Klapper 2016-11-09 17:47:12 UTC
...or whatever other place your distribution puts that file. :)
Comment 5 Atri 2017-03-07 01:36:39 UTC
(In reply to André Klapper from comment #4)
> ...or whatever other place your distribution puts that file. :)

Hi André,
If I can answer that, since I also see the problem all the time, executing

> /usr/lib/goa-daemon --replace

solves the issue (temporarily). I still get the same problem sometimes upon restarting my laptop or after wake up from suspend, but in each case executing the above seems to resolve it. Any suggestion on how not to hit the problem at all will be extremely gratifying, since this problem has bugged me since 3.20.x, I think.

I do get a bunch of messages when doing that, which may be helpful (or not, I am not really sure):

goa-daemon-Message: goa-daemon version 3.23.91 starting

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id: assertion 'tp_proxy_get_invalidated (self) == NULL' failed

(goa-daemon:32613): GLib-GIO-CRITICAL **: g_task_return_error: assertion 'error != NULL' failed

(goa-daemon:32613): GLib-GIO-CRITICAL **: g_task_propagate_boolean: assertion 'task->result_set == TRUE' failed

(goa-daemon:32613): goa-daemon-CRITICAL **: is_authorization_error: assertion 'error != NULL' failed

(goa-daemon:32613): GLib-CRITICAL **: g_error_free: assertion 'error != NULL' failed
Comment 6 Youssef 2017-06-06 10:59:17 UTC
I have the same exact problem, and the workaround of running "goa-daemon --replace" is only very temporary. This reliably happens nearly every single day.

I'm happy to provide more info but need some direction from a dev about what would be useful.

My system:
Fedora 25
Gnome 3.22.2 (From Gnome Settings -> Details)
Evolution 3.22.6 (From About menu)
Gnome Online Accounts 3.22.5 (from "dnf info")
Comment 7 Youssef 2017-06-06 11:00:24 UTC
I forgot to include in my previous comment:

I also get timeouts for a Nextcloud account that I have setup through GOA.
Comment 8 Debarshi Ray 2017-06-06 16:47:00 UTC
Did you happen to log out/in without a reboot?

Does this help:
https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Debugging ?
Comment 9 Debarshi Ray 2017-06-06 17:03:19 UTC
(In reply to Atri from comment #5)
> goa-daemon-Message: goa-daemon version 3.23.91 starting
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): tp-glib-CRITICAL **: tp_proxy_add_interface_by_id:
> assertion 'tp_proxy_get_invalidated (self) == NULL' failed
> 
> (goa-daemon:32613): GLib-GIO-CRITICAL **: g_task_return_error: assertion
> 'error != NULL' failed
> 
> (goa-daemon:32613): GLib-GIO-CRITICAL **: g_task_propagate_boolean:
> assertion 'task->result_set == TRUE' failed
> 
> (goa-daemon:32613): goa-daemon-CRITICAL **: is_authorization_error:
> assertion 'error != NULL' failed
> 
> (goa-daemon:32613): GLib-CRITICAL **: g_error_free: assertion 'error !=
> NULL' failed

I thought bug 766733 fixed a bunch of weird problems with the Telepathy bridge in 3.20. Maybe it ended up breaking something?

Do you have some Telepathy accounts configured? Is the "chat" switch on or off for those? I do have a Jabber account setup here, but I don't see these.
Comment 10 Debarshi Ray 2017-06-06 17:08:40 UTC
As per https://bugzilla.gnome.org/show_bug.cgi?id=766733#c57, we never fixed the tp-glib-CRITICALs, but the GLib-GIO-CRITICALs are troubling.
Comment 11 Atri 2017-06-06 21:16:18 UTC
(In reply to Debarshi Ray from comment #9)
> 
> I thought bug 766733 fixed a bunch of weird problems with the Telepathy
> bridge in 3.20. Maybe it ended up breaking something?
> 
> Do you have some Telepathy accounts configured? Is the "chat" switch on or
> off for those? I do have a Jabber account setup here, but I don't see these.

I do have an IRC account set up for online-accounts, and chat enabled for it. For both my google accounts, chat is turned off. Those are all the accounts I have configured via g-o-a.
Comment 12 Debarshi Ray 2017-06-07 09:43:44 UTC
(In reply to Atri from comment #11)
> I do have an IRC account set up for online-accounts, and chat enabled for
> it. For both my google accounts, chat is turned off. Those are all the
> accounts I have configured via g-o-a.

Ok. And which version of g-o-a are you running?

Does the '"can't get access token" ... timeout...' failure happen after you have logged out/in without a reboot?
Comment 13 Atri 2017-06-07 15:43:13 UTC
(In reply to Debarshi Ray from comment #12)
> (In reply to Atri from comment #11)
> > I do have an IRC account set up for online-accounts, and chat enabled for
> > it. For both my google accounts, chat is turned off. Those are all the
> > accounts I have configured via g-o-a.
> 
> Ok. And which version of g-o-a are you running?
>

3.24.0 as of now.
 
> Does the '"can't get access token" ... timeout...' failure happen after you
> have logged out/in without a reboot?

Yes it does. Also, I actually end up needing to reboot the machine to get a working connection via goa once I enter the "can't get access token" state. Multiple logins/logouts don't help.
Comment 14 Debarshi Ray 2017-06-07 16:45:50 UTC
(In reply to Atri from comment #13)
> > Does the '"can't get access token" ... timeout...' failure happen after you
> > have logged out/in without a reboot?
> 
> Yes it does. Also, I actually end up needing to reboot the machine to get a
> working connection via goa once I enter the "can't get access token" state.
> Multiple logins/logouts don't help.

Then this is a duplicate of bug 764029
Comment 15 Debarshi Ray 2017-06-07 16:46:02 UTC

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