Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Learn More

zombie calendar event

  • 3 odpovědi
  • 1 má tento problém
  • 40 zobrazení
  • Poslední odpověď od mikebrady60

more options

Since v.91, I've had a calendar entry that was originally in Google Calendar, attached via the Provider for Google Calendar, that has been deleted EVERYWHERE but constantly pops up a notification that it was changed on the server, and offers a 'delete anyway' button (warning that it might affect the server) and a 'discard my changes and reload' button. NEITHER WORKS. The event is long gone from the calendar at Google, and it doesn't appear in the calendar in Thunderbird that is connected to Google, but the notice keeps popping up and blocks all other use until I click "delete anyway." Clicking "discard and reload" immediately re-presents the notice.

No other writable calendar exists.

Is this a case where I need to save/back up my mail data and ONLY my mail data, uninstall Thunderbird with extreme prejudice, and start over from scratch? If so, that's a serious failure of v.91. Or do I need to delete EVERYTHING (since I'm using IMAP the cache should eventually reload) and start over?

Since v.91, I've had a calendar entry that was originally in Google Calendar, attached via the Provider for Google Calendar, that has been deleted EVERYWHERE but constantly pops up a notification that it was changed on the server, and offers a 'delete anyway' button (warning that it might affect the server) and a 'discard my changes and reload' button. NEITHER WORKS. The event is long gone from the calendar at Google, and it doesn't appear in the calendar in Thunderbird that is connected to Google, but the notice keeps popping up and blocks all other use until I click "delete anyway." Clicking "discard and reload" immediately re-presents the notice. No other writable calendar exists. Is this a case where I need to save/back up my mail data and ONLY my mail data, uninstall Thunderbird with extreme prejudice, and start over from scratch? If so, that's a serious failure of v.91. Or do I need to delete EVERYTHING (since I'm using IMAP the cache should eventually reload) and start over?

Zvolené řešení

Thanks for the suggestions, and sorry for the long delay. Life happened...

I tried the Google Calendar reconnection. No joy. I use the Google calendar as my home calendar so things are shared among all of my devices. Yes, I know, Google is reading my mail (which is fairly minimal at gmail - I have other accounts) and watching my calendar, but there's no way to avoid that in practice if I want it synced reliably across multiple devices including the non-Apple phone; it's going to have to reside on somebody's server. The default Home Calendar is local to the device Thunderbird is installed on, and I've in fact had problems with things accidentally going there if active, and therefore not syncing and getting effectively lost. I did check for that when the zombie appeared, and it was not on the Home Thunderbird calendar.

Ultimately, I realized that I could use the old-fashioned method I normally use only when setting up a new computer. Found a backup of my full profile (I make one every few months) from before the problem appeared, deleted my current profile and restored it from the older one. After reconnecting to Google, the calendar repopulated (took most of a day) with my current events and the zombie was finally gone. This was one time when I was glad I use IMAP connections rather than POP, so eventually all of my email was still there. So it's solved in practice, but I still don't know what happened.

Thanks for the responses.

Přečíst dotaz v kontextu 👍 0

Všechny odpovědi (3)

more options

Have you tried the following to see if it clears the issue? Thunderbird can now connect up to Google without any addons. Suggest you reset Google Calendar. Disable the addon 'Provider for Google Calendar' Remove the current Google Calendar

Then recreate the calendar Menu app icon > New > Calendar > On the Network Enter details of gmail email address, select the calendar and click on Subscribe You will get a prompt from Google to allow access.

Additional info: https://support.mozilla.org/en-US/kb/creating-new-calendars

Upravil uživatel Toad-Hall dne

more options

re :No other writable calendar exists.

Thunderbird has a default 'Home' calendar - are you saying you deleted it or it's in the left list of calendars but you just do not use it?

more options

Zvolené řešení

Thanks for the suggestions, and sorry for the long delay. Life happened...

I tried the Google Calendar reconnection. No joy. I use the Google calendar as my home calendar so things are shared among all of my devices. Yes, I know, Google is reading my mail (which is fairly minimal at gmail - I have other accounts) and watching my calendar, but there's no way to avoid that in practice if I want it synced reliably across multiple devices including the non-Apple phone; it's going to have to reside on somebody's server. The default Home Calendar is local to the device Thunderbird is installed on, and I've in fact had problems with things accidentally going there if active, and therefore not syncing and getting effectively lost. I did check for that when the zombie appeared, and it was not on the Home Thunderbird calendar.

Ultimately, I realized that I could use the old-fashioned method I normally use only when setting up a new computer. Found a backup of my full profile (I make one every few months) from before the problem appeared, deleted my current profile and restored it from the older one. After reconnecting to Google, the calendar repopulated (took most of a day) with my current events and the zombie was finally gone. This was one time when I was glad I use IMAP connections rather than POP, so eventually all of my email was still there. So it's solved in practice, but I still don't know what happened.

Thanks for the responses.