Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Cari Bantuan

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.

Pelajari Lebih Lanjut

Solution for Thunderbird 25.0 crashes after installing provider 1.0.2

  • 2 balas
  • 1 memiliki masalah ini
  • 1 kunjungan
  • Balasan terakhir oleh mikesnr

more options

After noticing that provider had stopped working I checked and found that the old Google API had been discontinued. The provider author advised to change to provider 1.0.2 as an interim measure but to await 1.0.3. I did this and Thunderbird crashed every time it started. the solution for me was to upgrade to latest 31.2 Thunderbird and then opt to accept latest lighting add-on during the set up. Result is every thing now back to normal. Whew that was scary! Many Thanks to the provider author for posting the note about demise of old Google API. My system was running Win 8.1

After noticing that provider had stopped working I checked and found that the old Google API had been discontinued. The provider author advised to change to provider 1.0.2 as an interim measure but to await 1.0.3. I did this and Thunderbird crashed every time it started. the solution for me was to upgrade to latest 31.2 Thunderbird and then opt to accept latest lighting add-on during the set up. Result is every thing now back to normal. Whew that was scary! Many Thanks to the provider author for posting the note about demise of old Google API. My system was running Win 8.1

Solusi terpilih

I prefer CalDav. Then you don't need Provider and that's one less thing that has to be kept to the appropriate version.

Note that this web page:

https://blog.mozilla.org/calendar/2013/09/google-is-changing-the-location-url-of-their-caldav-calendars/

is over a year old, so the version numbers given there are out of date. However it is still good for the process of connecting your Calendar.

Past versions of Lightning are here:

https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/

which is useful if you ever need to run other than the very latest Thunderbird.

Baca jawaban ini dalam konteks 👍 1

Semua Balasan (2)

more options

Solusi Terpilih

I prefer CalDav. Then you don't need Provider and that's one less thing that has to be kept to the appropriate version.

Note that this web page:

https://blog.mozilla.org/calendar/2013/09/google-is-changing-the-location-url-of-their-caldav-calendars/

is over a year old, so the version numbers given there are out of date. However it is still good for the process of connecting your Calendar.

Past versions of Lightning are here:

https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/

which is useful if you ever need to run other than the very latest Thunderbird.

more options

Thanks Zenos, Its just as well you posted your response as several days later a bug showed up in new provider 1.0.2 that has been acknowledged by the author. the Google calendar events dissappear even though the sync is working without error. The author is working on a fix. In the mean time I took up your suggestion to set up a caldav link to Google calendar (note there is a new caldav address as old one was changed by Google). After some fiddling around with the address and inserting my Gmail address into the caldav address string (I missed this the first time reading the notes on the link) it works great. So all back to normal. I disabled the provider exentsion for now and deleted the original calendar uaing that link