1505822 - no calendar after update Thunderbird 52.9.1 > 60.3.0

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Worcester12345]

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

Steps to reproduce:

Production computer.

Accepted Thunderbird update from Help:About, and let it run 52.9.1 > 60.3.0.

Now no calendar after update Thunderbird 52.9.1 > 60.3.0

Go to Tools:Addons, and Lightning is gone.

Search for Lightning, and it says it is incompatible. 

What now?


Actual results:

Thunderbird restarted, but no calendar, no Lightning. It says Lightning not compatible.


Expected results:

It should just work.

Comment 1

[Jorg K (CEST = GMT+2)]

(In reply to Worcester12345 from comment #0)
> What now?
Very simple fix: https://support.mozilla.org/en-US/kb/calendar-updates-issues-thunderbird (last section).
Summary: Reset pref extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103}, restart, done.

Comment 2

[Wayne Mery (:wsmwk)]

FYI the definition of blocker https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity

It's our well known issue

Comment 3

[Worcester12345]

(In reply to Jorg K (GMT+1) from comment #1)
> (In reply to Worcester12345 from comment #0)
> > What now?
> Very simple fix:
> https://support.mozilla.org/en-US/kb/calendar-updates-issues-thunderbird
> (last section).
> Summary: Reset pref
> extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103},
> restart, done.

More of a workaround than actually fixing the code to eliminate the problem, right?


(In reply to Wayne Mery (:wsmwk) from comment #2)
> FYI the definition of blocker
> https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity
> 
> It's our well known issue

Agree on both counts! Thanks.

Comment 4

[Worcester12345]

If not the same exact thing, this one is very similar:
https://bugzilla.mozilla.org/show_bug.cgi?id=1473873

Comment 5

[Worcester12345]

Was this issue ever resolved so the "workaround" is no longer necessary?

Resolving as "WORKSFORME" because of the workaround, not that there was a known fix.

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to Worcester12345 from comment #5)

Was this issue ever resolved so the "workaround" is no longer necessary?

In short, no. From the blockers of bug 1215828, only bug 1484532 changed to FIXED since you filed this bug report. And it a) doesn't have a patch b) is only relevant to Linux.

Resolving as "WORKSFORME" because of the workaround, not that there was a known fix.

You would set WORKSFORME if you haven't seen the issue again, not because there is a workaround ;)