Closed Bug 1608754 Opened 6 years ago Closed 5 years ago

Lightning 68.3.1.1 doesn't find calendar data - Jan 12, 2020

Categories

(Calendar :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mike_piehl, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

  1. restarted TB, 68.4.1 (32b)
  2. tried https://support.mozilla.org/en-US/kb/calendar-updates-issues-thunderbird#w_lightning-disappears-after-a-thunderbird-update-release-and-beta-versions -- Lightning disappears after a Thunderbird update
    no surprise, Lightning and it's data are different
  3. tried uninstalling Lightning and reinstalling again

Actual results:

Thunderbird version 68.4.1 (32b), released Jan 9, installed?
Today, Jan 12 after Lightning is updated (Jan 12) when Calendar is opened, no data/entries are displayed.

Expected results:

I know That TB and Lightning updates get tested extensively, for 10 years anyway.
Updates usually work without user interference.

Component: Untriaged → General
Product: Thunderbird → Calendar
Version: 68 → unspecified

Today I rebooted a number of times, and now 2225 UTC after disabling a sound card and rebooting Google calendar provider popped up asking for authorization. I think I did that already long time ago, once. Before doing that I checked TB's calendar and it was populated. So I'm going to guess and say it's working.

So I didn't do anything other than my normal routine. So this is really disappointing, but I'm happy anyway.

WFM per previous comment.

Thunderbird & Lightning developers decided some time ago that issues regarding Provider for Google Calendar are no longer tracked in Bugzilla. Please refer to instructions listed on its extension homepage https://github.com/kewisch/gdata-provider/wiki/FAQ#bugs-and-limitations in case of problems.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.