Closed Bug 1596919 Opened 5 years ago Closed 3 years ago

Calendar not shown in list and "TypeError: currentView(...) startDay is null"

Categories

(Calendar :: Calendar Frontend, defect)

Product:
Calendar
Component:
Calendar Frontend
Version:
Lightning 68
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: martin.trinks, Unassigned)

References

Details

Attachments

(3 files)

Calendar list.jpg
79.56 KB, image/jpeg
Details
Error Console.jpg
44.68 KB, image/jpeg
Details
grafik.png
77.81 KB, image/png
Details
Attached image Calendar list.jpg —

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

Steps to reproduce:

Nothing - just at startup.

But in my case the problem disappears when disabling (deinstalling) Lightning and enabling (installing) it again, but it appears again after closing Thunderbird and open it again.

Thunderbird: 68.2.2
Lightning: 68.2.2

Actual results:

No calendars are shown in the calender list (but the events in the calendar).
On the same time there is somme error in the log:
"TypeError: currentView(...) startDay is null"

Also the calendar events can not be edited or deleted and new ones can not be added. Trying this the following errors occur in the log:
"NS_ERROR_NOT_INITIALIZED: Calendar list has no composite calendar yet"

Expected results:

The calendars should be shown in the calendar list and is should be possible to edit, add and remove events.

Attached image Error Console.jpg —
Severity: normal → critical
OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop

The problem seems to be related to the CardBook Add-on, disabling this and restarting Thunderbird "solves" the problem.

Could anyone give me some hint how to check which part of the CardBook code causes the problem?

I have to revise my last comment, the problem is not related to the CardBook Add-on, restarting Thunderbird the same error as documented above occurs (without any other Add-ons enabled).

Hi,
I am experiencing exactly these problems. At first, like you, I thought this was related to add-ons but now I have come to the conclusion that it's a TB / Lightning issue.
I have a lengthy and continuing discussion here https://support.mozilla.org/en-US/questions/1273975?utm_campaign=questions-reply&utm_medium=email&utm_source=notification

I'm on the "release" update channel and currently using TB 68.3.1 (64b) with Lightning 68.3.1.1.

I see exactly the same symptoms as you, and as you describe, I can get the calendar to function by removing and then re-installing Lightning. So I exit TB as little as possible and use hibernation instead of closing Windows sessions.

Please see recent posts in the forum https://support.mozilla.org/en-US/questions/1273975?page=2
We find that "Help > Restart with Add-ons Disabled" followed by exit and normal start restores calendar functionality.
Another contributor, Paulo F., suggests this may indicate that the bug lies somewhere in loading the add-ons, and that the safe mode cleans something up. I agree.

As John above re forum . I have the same issue and the workround above works too on the tower I am using now . Not so the laptop where all is well . John asked about the update histories for both machines which in fact have been different . The tower has gone via the 68 series and is now on 72.0.1 whereas the laptop was "stuck" [ without detriment ] at around 63 until this weel when it caught up and Lightening works normally there whilst not even with 72.0.1 on the tower . Both are set up to accept updates automatically and both are on the latest versions of W10 [ which I concede may differ ] .

For me the issues is gone, I had no problem with 68.3 and 68.4.

Thanks for the update Martin Trinks. Not my case unfortunately!
Just out of interest, have the errors you were seeing in the console stopped?

Yes, the errors mentionded in this bug have stopped.

I only have the following error, but I think this is related to another bug:
date value is not finite in DateTimeFormat.format() @ minimonth.xml:727

Attached image grafik.png —

The current output in my error console in TB, which was started

Flags: needinfo?(a_dennig)

I have exactly the same problem as Martin Trinks reported. I have noticed this problem since TB version 68.x since january 2020.

When i start TB in normal mode with activated lightning, i see the calendar entries in that way, as the picture shows above in this report. I am not be able to edit my calendar entries. I can open the editor, but i'm not able to save the changes and i cannot delete or add new entries to the calendar.

The only way to do this with TB is to restart TB in "safe mode". There is no lightning active. Now, i can close TB in safe mode and restart TB in "normal mode". Now, all entries in the calendar are shown normaly and i can change them normaly.
If i close TB and restart it again in normal mode, the problem raises again.

My actual error console show these messages (most times, only "TypeError: currentView(...).startDay is null" appears).

Flags: needinfo?(a_dennig)

I have this same problem (as a.dennig) as well: Thunderbird 68.5.0, Lightning 68.5.0.
same console error messages, same remediation.

I have the same problem (Thunderbird 68.5.0, Lightning 68.5.0). The issue is not present in 68.3.1.1.

Weirdly enough, it is sufficient to select 'restart in safe mode', and then cancel the safe mode dialog window. The next time I start Thunderbird, Lightning works for one time, but not across further restarts.

I had the same issue. I could get the calendar to display properly if I used "pkill thunderbird", the next startup it would work, but not after a "clean" shutdown.

Eventually I found that "Reset toolbars and controls" from safe mode fixed it for me:
https://support.mozilla.org/en-US/kb/safe-mode-thunderbird

@mo - that seems weird but I get the same result. Presumably just starting in "safe mode" is enough to clear the problem that comes back at some time after re-starting in normal mode. A help anyway, makes the work-around quicker. Thanks!

@dennis - thanks. I tried "Reset toolbars and controls" but the problem came back after a second restart. Glad it fixed it for you though and thanks for your info!

Hi folks,
Good news, thanks to dennis who pointed me in the right direction.
I've just posted over in the forum, https://support.mozilla.org/en-US/questions/1273975?page=3#answer-1295812 my findings.

It turns out that the problem I've been experiencing comes from choosing the option "Events in current view", for the list of events shown above the calendar. All I had to do was choose another option such as "Next 7 days".

This bug is perfectly reproducible. All you have to do is to select "Events in current view" and restart TB in normal mode.

Now that the problem is properly described, could we ask for it to be solved, or else the option "Events in current view" needs to be disabled. It seems to have caused problems for a lot of people, and wasted incalculable hours of time, since appearing, I think about 68.1 or 68.2. It is however a useful option so I would vote for a fix rather than removal.

@John Thompson:
Thanks a lot for your posted workaround here. This works very fine vor me and now, the calendar of TB in normal mode is working properly and also, when restarting TB again and again normaly....

I agree to you, to have a fixing for the corrupt option.

Wow, that's a great workaround! Thanks John!

Thank you John for finding the setting that was causing the issue. It should be much easier to find the bug, fix, and write a test for it now that it can be reproduced by anyone.

Yes Dennis, let's hope this will enable the bug to be identified. It certainly proves that it exists!

Some additional info: I confirm that selecting the "Events in current view" option, causes the "TypeError: currentView(...).startDay is null - calFilter.js:513:28" error we've been seeing in the console. This error does not appear when I select "Next 14 days", for example, instead.

Unfortunately there are other users with a similar problem (I mean similar symptoms, though not necessarily identical) who haven't seemingly been helped by this work-around. It seems to me possible that the bug at the root of this could be triggered as well, by other settings or usages. It also seems possible to me that this bug was introduced in the early versions of TB 68. I saw it late November and I rarely change settings. At least we now know why people have been reporting it from different versions since then (or, like Martin Trinks, are no longer seeing it). It's just a question of when you do something, perfectly "legal", that triggers the bug, such as selecting "Events in current view".

I will do what I can to check other settings, beginning with other choices for the events list.

Maybe a duplicate of bug 1556792?

Confirming and adjusting version the bug has been observed first in by duplicates. Keeping this bug report as it has the most relevant details.

Status: UNCONFIRMED → NEW
Component: General → Calendar Frontend
Ever confirmed: true
OS: Windows 10 → All
Hardware: Desktop → All
Version: Lightning 70 → Lightning 68

To everyone who has experienced this issue in the past: Can you still reproduce this issue with Thunderbird 78 or Thunderbird 91 (which is not yet distributed via automatic updated)?

I haven't been able to reproduce this bug with Thunderbird 78.13.0 on Ubuntu. I selected "Events in current view" and don't see "TypeError: currentView(...) startDay is null" in the console and the calendar seems to be fully functional. I've even tried restarting TB a few times.

Resolving this as WORKSFORME as it cannot be reproduced in Thunderbird 78 or 91. Feel free to open a new bug report if you encounter a similar issue.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME

(In reply to Martin Schröder [:mschroeder] from comment #29)

To everyone who has experienced this issue in the past: Can you still reproduce this issue with Thunderbird 78 or Thunderbird 91 (which is not yet distributed via automatic updated)?

Hi all,
Sorry for late reply. Running 78.13.0 on Windows 10. Like dennis, I can no longer reproduce the bug by selecting "Events in current view".
Have relaunched TB several times and changed the list selection option several times.
So, WORKSFORME !
Good job, well done and thanks
John

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: