Thunderbird / Calendar v68.2.0 breaks Provider for Google Calendar (v68.0)
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: hornadw, Unassigned)
Details
Attachments
(1 file)
10.58 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36
Steps to reproduce:
Updated Thunderbird to v68.2.0
Actual results:
Provider now prompts for login every time synchronize is requested, or a new Google calendar entry is attempted to be created. Cannot create new entries.
Expected results:
- Should not prompt for login (Stay Signed In is checked).
- Should successfully synchronize.
- Should allow new Google entries to be created.
Comment 2•5 years ago
|
||
Hi,
running Windows latest update 10.0.17134.1069
Same problem here. I updated TB to 68.2, I'm on the "release" channel, on purpose to hopefully avoid this sort of major pain and waste of time.
Which it is for me. I have not only lost access to Google calendar but also my home calendar.
I can't create any calendar entry, calendar is empty (except for public holidays and some Home calendar entries that I can't edit) and Today Pane also. It doesn't even show today's date!!
In calendar pane I can't switch from the current (Multiweek) view to any other.
This all seems to be far beyond what I'd expect as the consequences of deactivating the Provider for Google calendar.
No problem (at present) picking up gmail with pop3.
I would also like to say that "release" channel users really should have been warned that 68.2 would deactivate the Google calendar provider.
I'm currently contemplating re-installing the previous version of TB. Any advice welcomed.
Comment 3•5 years ago
|
||
This is turning into a MAJOR BIND. running 68.2 just once has rendered the user profile unusable with the previous version 68.1.2 !!
No way of easily rolling back... It's looking like I'll have to re-configure everything, or hope I can use a recent backup.
Staying with TB after this is going to be a considerable act of faith.
Comment 4•5 years ago
|
||
I went back to 68.2.
An update for the Provider for Google Calendar is now available.
It is working partially, in that GC entries are now appearing in the Calendar pane (or is it "pain" ...?)
However, can't create entries, edit or, I suspect, delete. The list of calendars normally shown on the left of Calendar pane is empty (not even Home) and the Today Pane is still totally broken.
Comment 5•5 years ago
|
||
Hi,
Please note that Provider for Google Calendar dev and support has been relocated here:
https://github.com/kewisch/gdata-provider (source: http://wiki.mozilla.org/Calendar:GDATA_Provider)
Therefore if you have any issue with Provider for Google Calendar (or related to it) the best is to raise a ticket at GitHub instead of Bugzilla (which is no longer used for Provider for Google Calendar support) :
https://github.com/kewisch/gdata-provider/issues
Having a quick look around, I found this bug 1592407 comment 22 which is related to "Google services are currently disrupted: OAuth2 failure when using Google Account (Gmail authentication using OAuth2 stopped working) - Affects account creation of IMAP accounts and 3rd-party add-on "Provider for Google Calendar" - Workaround: Comment #22"
The fix suggested is to set general.useragent.compatMode.firefox to true as posted here https://github.com/kewisch/gdata-provider/issues/26#issuecomment-547994463
This fix is confirmed to sort Google IMAP authentication issues so it may work as well for Calendar...
May be worth a try to see if that can fix your Google Calendars issue as reported in this bug...
Hope that help.
Regards,
Richard
Updated•5 years ago
|
Comment 7•5 years ago
|
||
(In reply to Richard Leger from comment #5)
Hi,
Please note that Provider for Google Calendar dev and support has been relocated here:
https://github.com/kewisch/gdata-provider (source: http://wiki.mozilla.org/Calendar:GDATA_Provider)Therefore if you have any issue with Provider for Google Calendar (or related to it) the best is to raise a ticket at GitHub instead of Bugzilla (which is no longer used for Provider for Google Calendar support) :
https://github.com/kewisch/gdata-provider/issuesHaving a quick look around, I found this bug 1592407 comment 22 which is related to "Google services are currently disrupted: OAuth2 failure when using Google Account (Gmail authentication using OAuth2 stopped working) - Affects account creation of IMAP accounts and 3rd-party add-on "Provider for Google Calendar" - Workaround: Comment #22"
The fix suggested is to set general.useragent.compatMode.firefox to true as posted here https://github.com/kewisch/gdata-provider/issues/26#issuecomment-547994463
This fix is confirmed to sort Google IMAP authentication issues so it may work as well for Calendar...
May be worth a try to see if that can fix your Google Calendars issue as reported in this bug...Hope that help.
Regards,
Richard
@Richard
Thanks very much for the info. I've set the compatmode parameter to true but no noticeable change. I'm now systematically getting the Google login dialog which I rarely had before (use master password).
To be honest I'm now wondering whether the problems I have really relate to the provider, which was updated during the day and now works.
There seems to be general damage in Lightning which persists as previously described. I'll try and find a more suitable forum.
Comment 8•5 years ago
|
||
(In reply to John Thompson from comment #7)
(In reply to Richard Leger from comment #5)
I've set the compatmode parameter to true but no noticeable change.
Have you tried to completetly close/exit TB and restart it after the change applied?
I'm now systematically getting the Google login dialog which I rarely had before (use master password).
I suspect first time you may need to re-enter your Google password and have it saved again perhaps if option offered to you. Possibly for each GCalendar...
You could also try to delete Google password from saved password beforehand...
Those are possible workaround...
A fix for bug 1592407 has been deployed which may be a possible fix for this bug. To be confirmed.
To be honest I'm now wondering whether the problems I have really relate to the provider, which was updated during the day and now works.
As it is related to Google Calendar I would suggest to always open a ticket here first:
https://github.com/kewisch/gdata-provider/issues
You can refer to this bug when opening related new issue on GitHub...
There seems to be general damage in Lightning which persists as previously described. I'll try and find a more suitable forum.
If you can reproduce issue with a CalDav calendar provider then it may likely be a Lightning issue else likely a gdata-provider issue... the hard part being able to distinguish where the bug lie in gdata or lightning... but the gdata-provider developer may be better placed to help on that matter... in any case he also work on Lightning from my understanding...
Reporter | ||
Comment 9•5 years ago
|
||
Just to confirm or reiterate, from https://github.com/kewisch/gdata-provider/issues/26 :
In TB about:config,
[quoting olegch:]
Changing "general.useragent.compatMode.firefox" preference to true fixes the issue, google authentication works again.
[end quote:]
This fixed the problem for me.
Comment 10•5 years ago
|
||
John,
As Tom confirmed fix suggested works for him, if none of what I sugested worked, then try to simply tidisable the master password temporarily... as another possibility...
If nothing works for you, then I would suggest to file a follow up bug as this one is now considered fixed and closed.
Regards,
Comment 11•5 years ago
|
||
I confirm that changing "general.useragent.compatMode.firefox" preference to true fixes the issue, google authentication works again.
Thank you :-)
Description
•