Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1817086 - Failed to obtain an access token from Google for “account”: Timeout was reached
Summary: Failed to obtain an access token from Google for “account@domain.tld”: Timeou...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-online-accounts
Version: 32
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-25 14:42 UTC by Alex Chvatal
Modified: 2021-05-25 17:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:55:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Alex Chvatal 2020-03-25 14:42:47 UTC 
Description of problem:
Gnome doesn't sync calendars for Google accounts set up in Gnome Online Accounts. After a Google account is added, the account's calendars do not show up in Evolution or gnome-calendar.

Evolution displays an error message:

> Failed to connect “account”
> 
> Failed to obtain an access token for “account”: Timeout was reached

Version-Release number of selected component (if applicable):
gnome-online-accounts-3.34.1-1.fc31.x86_64
evolution-3.34.4-1.fc31.x86_64
gnome-calendar-3.34.2-1.fc31.x86_64

How reproducible:
every time

Steps to Reproduce:
1. Open the Gnome settings app
2. click on Online Accounts
3. Add a Google account, enter email and press enter.
4. Enter username and pin+token password (or use kerb ticket)
5. Click on Allow to allow Gnome to access the account
6. Wait something like 4.5 minutes for the operation to complete

Actual results:
No calendars for the account are visible in Evolution or gnome-calendar and its events don't show up in the gnome-shell daily overview (when you click on the time in the top bar).

Expected results:
The calendars are present.

Additional info:
Comment 1 David Quiñones 2020-04-03 22:55:15 UTC 
Same here. I had events working perfectly during the morning. At noon I noticed my events disappeared from the calendar panel in Gnome Shell, so I removed my account to add it again experiencing the same that you are reporting. This is the message that appears in journalctl when opening gnome-calendar

`gnome-calendar[15229]: source_credentials_required_cb: Failed to authenticate 'xxxxx': Failed to obtain an access token for “xxxxxx”: Timeout was reached`
Comment 2 David Quiñones 2020-04-27 03:06:13 UTC 
It works now, I don't know if changing to another network had something to do with it, which is very weird (I ran a VM in the previously failing network and it worked just fine in it, but not in my main machine).
Comment 3 Brian J. Murrell 2020-05-07 15:54:46 UTC 
I get this fairly frequently for my Google Calendar and GMail by way of GoA.
Comment 4 Alex Chvatal 2020-05-14 13:02:50 UTC 
This problem went away for a while but is back now.

Using:
gnome-online-accounts-3.36.0-1.fc32.x86_64
evolution-3.36.2-1.fc32.x86_64
gnome-calendar-3.36.1-1.fc32.x86_64
Comment 5 Alex Chvatal 2020-06-25 12:33:27 UTC 
This problem had gone away for a while again but is back again.

Using:
evolution-3.36.3-1.fc32.x86_64
gnome-online-accounts-3.36.0-1.fc32.x86_64
gnome-calendar-3.36.2-1.fc32.x86_64
Comment 6 Debarshi Ray 2021-04-16 21:17:24 UTC 
Does this help:
https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Debugging ?
Comment 7 Fedora Program Management 2021-04-29 17:09:41 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 8 Ben Cotton 2021-05-25 17:55:09 UTC 
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.