1556792 - Startup error and blank calendar display when week view is visible

Status: RESOLVED WORKSFORME

(Calendar :: Calendar Frontend, defect)

Description

[Stefan Sitter [:ssitter]]

Attachment: week-view.png

Thunderbird 69.0a1 (20190604091847) with Lightning 7.1a1 on Windows 10.

History: Switch to week view. Create an event and verify that event is displayed in week view. Restart Thunderbird.

Error: Week view is displayed but blank, i.e. no rows and columns are displayed. Error Console shows:

dayBox.startLayoutBatchChange is not a function calendar-multiday-base-view.js:1118

TypeError: this.mDateColumns[0] is undefined calendar-multiday-base-view.js:1379:30

[Exception... "[JavaScript Error: "this.mDateColumns[0] is undefined" {file: "chrome://calendar/content/calendar-multiday-base-view.js" line: 1379}]'[JavaScript Error: "this.mDateColumns[0] is undefined" {file: "chrome://calendar/content/calendar-multiday-base-view.js" line: 1379}]' when calling method: [calIAlarmServiceObserver::onRemoveAlarmsByItem]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: resource://calendar/modules/utils/calDataUtils.jsm :: notify :: line 40" data: yes]
STACK: notify@resource://calendar/modules/utils/calDataUtils.jsm:40:31
removeAlarmsForItem@resource://calendar/calendar-js/calAlarmService.js:397:25
findAlarms/onGetResult/<@resource://calendar/calendar-js/calAlarmService.js:521:43
run@resource://calendar/modules/utils/calIteratorUtils.jsm:79:38
fetchOverlay@resource:///modules/Overlays.jsm:425:9
load@resource:///modules/Overlays.jsm:93:22
load@resource:///modules/Overlays.jsm:40:14
registerNonBootstrapped/<@chrome://messenger/content/parent/ext-legacy.js:161:20
registerNonBootstrapped@chrome://messenger/content/parent/ext-legacy.js:159:23
asynconManifestEntry@chrome://messenger/content/parent/ext-legacy.js:42:20
asyncEmitManifestEntry@resource://gre/modules/ExtensionCommon.jsm:1421:18
asyncrunManifest/<@resource://gre/modules/Extension.jsm:1767:37
addStartupStatePromise@resource://gre/modules/Extension.jsm:1502:13
addPromise@resource://gre/modules/Extension.jsm:1761:26
runManifest@resource://gre/modules/Extension.jsm:1766:9
startup/<@resource://gre/modules/Extension.jsm:1990:48
addStartupStatePromise@resource://gre/modules/Extension.jsm:1502:13
startup@resource://gre/modules/Extension.jsm:1989:14
async*startup@resource://gre/modules/Extension.jsm:1313:27
callBootstrapMethod@resource://gre/modules/addons/XPIProvider.jsm:1742:33
startup@resource://gre/modules/addons/XPIProvider.jsm:1841:32
startup@resource://gre/modules/addons/XPIProvider.jsm:2325:39
callProvider@resource://gre/modules/AddonManager.jsm:193:31
_startProvider@resource://gre/modules/AddonManager.jsm:568:5
startup@resource://gre/modules/AddonManager.jsm:723:14
startup@resource://gre/modules/AddonManager.jsm:2787:26
observe@resource://gre/modules/addonManager.js:71:29
calDataUtils.jsm:43

Comment 1

[Stefan Sitter [:ssitter]]

With multiweek or month view the calendar is blank too but the error is different:

weekLabel is null calendar-month-base-view.js:501
relayout chrome://calendar/content/calendar-month-base-view.js:501
execute chrome://calendar/content/calendar-base-view.js:259
addItemsFromCalendar chrome://calendar/content/calendar-base-view.js:797
refresh chrome://calendar/content/calendar-base-view.js:776
setDateRange chrome://calendar/content/calendar-month-base-view.js:297
goToDay chrome://calendar/content/calendar-views.js:214
switchToView chrome://calendar/content/calendar-views-utils.js:288
ltnSwitch2Calendar chrome://lightning/content/messenger-overlay-sidebar.js:677
openTab chrome://lightning/content/messenger-overlay-sidebar.js:72
openTab chrome://messenger/content/tabmail.xml:608
restoreTab chrome://lightning/content/messenger-overlay-sidebar.js:99
restoreTab chrome://messenger/content/tabmail.xml:1085
registerTabType chrome://messenger/content/tabmail.xml:366
fetchOverlay resource:///modules/Overlays.jsm:425
load resource:///modules/Overlays.jsm:93
load resource:///modules/Overlays.jsm:40
registerNonBootstrapped chrome://messenger/content/parent/ext-legacy.js:161
forEach self-hosted:266
registerNonBootstrapped chrome://messenger/content/parent/ext-legacy.js:159
InterpretGeneratorResume self-hosted:1284
AsyncFunctionNext self-hosted:839

Comment 2

[Stefan Sitter [:ssitter]]

Works fine using Thunderbird 68.0a1 (20190520104136) with Lightning 7.0a1, i.e. only Lightning 7.1 seems affected.

Comment 3

[Alexander Kruth]

I've got the same issue using TB 68.2.1 with Ligthning 68.2.0. Workaround is to start in safe-mode and then restart, but on the next startup the problem is back. Is there any resolution?

Comment 4

[Martin Schröder [:mschroeder]]

Stefan, can you still reproduce this issue with Thunderbird 78? For me, it works as expected.

Comment 5

[Martin Schröder [:mschroeder]]

Alexander, can you still reproduce this issue with Thunderbird 78?

Comment 6

[Alexander Kruth]

Hi Martin, I am happy to confirm that this issue is no longer present with Thunderbird 68.10.0.

Comment 7

[Stefan Sitter [:ssitter]]

WFM using 84.0a1 (2020-11-03).