Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Events not updating after 114.4.1 upgrade

  • 1 reply
  • 1 has this problem
  • 50 views
  • Last reply by Mark Foley

Mark Foley
Mark Foley
more options

After upgrading Thunderbird client to version 114.4.1 on my Windows 10 computer, I no longer can see events. I am using a CalDAV server on Linux. I believe creating and updating events works on a different Linux client, but not on this Windows 10 client. In my error console I see the message, "Calendar: Could not find definition for Eastern Standard Time". I've read some posts where others had that same time zone issue and fixing that got their events to show up. Unfortunately, they did say how they fixed it. Perhaps that is my problem as well. How do I resolve this error (to start with)?

After upgrading Thunderbird client to version 114.4.1 on my Windows 10 computer, I no longer can see events. I am using a CalDAV server on Linux. I believe creating and updating events works on a different Linux client, but not on this Windows 10 client. In my error console I see the message, "Calendar: Could not find definition for Eastern Standard Time". I've read some posts where others had that same time zone issue and fixing that got their events to show up. Unfortunately, they did say how they fixed it. Perhaps that is my problem as well. How do I resolve this error (to start with)?

Chosen solution

I deleted and recreated the account. That seems to have fixed it.

Read this answer in context 👍 0

All Replies (1)

Mark Foley
Mark Foley Question owner
more options

Chosen Solution

I deleted and recreated the account. That seems to have fixed it.