Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

Events not updating after 114.4.1 upgrade

  • 1 wótegrono
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót 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)?

Wubrane rozwězanje

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

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (1)

more options

Wubrane rozwězanje

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