Google Calendar entries disappear after laptop resumes from sleep



6 years ago
4 years ago


(Reporter: jon, Unassigned)


Lightning 1.7
Windows 7




6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

After resuming from sleep, the calendar is empty and no events are fired. The calendar is not refreshed on the normal schedule and I have to stop and restart TB before normal functionality is resumed. Apart from this I haven't experienced other calendar problems.

I thought this might be a duplicate, but this other report is about iCal, not GData:

Actual results:

It doesn't happen every time the machine sleeps -- I suspect it only happens if the machine is asleep when the Provider has scheduled an update.

Expected results:

The calendar data should be refreshed and alerts should be raised normally.


6 years ago
OS: All → Windows 7
Hardware: All → x86_64

Comment 1

6 years ago
I have this problem too, also on Windows 7, using TB 16.0.1. The only way I know to see Google calendar events again once this happens is to close Thunderbird/Lightning, wait a few seconds, and then start the application again and wait for everything to load.

Comment 2

6 years ago
I have experienced the same behavior on both OS X 10.6.8 with TB 16.0.2 and Provider for Google Calendar v 0.17 and on windows XP SP3 (same version of TB and Provider)
There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version.

Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue.

Thank you for your understanding.

Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.