Closed danstowell closed 4 months ago
Thanks for reporting! Can you enable debug logging and share the exchange that occurs when you synchronize?
It looks like we haven't heard back on this issue, therefore we are closing this issue. If this problem persists in the latest version of Thunderbird and the Provider for Google Calendar, please re-open this issue.
Sorry for the slow reply, I only just worked out how to enable the debug logging. Here's my log - as you'll see, there's an "Assert failed" (same assert as in #709, for example). Perhaps that's not the issue but it's the only odd thing I can see:
Calendar: [calStorageCalendar] Timezones have been changed from 2023c to 2024a, updating calendar data. calStorageUpgrade.jsm:451
Calendar: [calGoogleSessionManager] Creating session [[MYUSERNAME]]@[[MYDOMAIN]] gdataSession.jsm:89
Calendar: [calStorageCalendar] Timezones have been changed from 2023c to 2024a, updating calendar data. calStorageUpgrade.jsm:451
Calendar: Could not find definition for /freeassociation.sourceforge.net/Tzfile/America/Denver CalTimezoneService.jsm:135
Calendar: Could not find definition for /freeassociation.sourceforge.net/Tzfile/America/Vancouver CalTimezoneService.jsm:135
Calendar: Could not find definition for /freeassociation.sourceforge.net/Tzfile/Europe/Jersey CalTimezoneService.jsm:135
Calendar: Could not find definition for /freeassociation.sourceforge.net/Tzfile/Europe/London CalTimezoneService.jsm:135
Calendar: Could not find definition for /freeassociation.sourceforge.net/Tzfile/Europe/Paris CalTimezoneService.jsm:135
Calendar: Could not find definition for HEL1206838800000 CalTimezoneService.jsm:135
Calendar: Could not find definition for LHR1206838800000 CalTimezoneService.jsm:135
Calendar: [calICSCalendar] Refreshing NLg CalICSCalendar.sys.mjs:706
Calendar: [calICSCalendar] Refreshing NL CalICSCalendar.sys.mjs:706
Calendar: [calICSCalendar] Refreshing Home CalICSCalendar.sys.mjs:706
Calendar: [calICSCalendar] Loading ICS succeeded, needs further processing: true 5 CalICSCalendar.sys.mjs:348
Calendar: [calICSCalendar] Parsing ICS succeeded for file:///home/[[ME]]/mycalfolder/NLg.ics CalICSCalendar.sys.mjs:412
Calendar: [calICSCalendar] Parsing ICS succeeded for file:///home/[[ME]]/mycalfolder/NL.ics CalICSCalendar.sys.mjs:412
Calendar: [calICSCalendar] Parsing ICS succeeded for file:///home/[[ME]]/mycalfolder/Home.ics CalICSCalendar.sys.mjs:412
Calendar: Ignoring attendee duplicate for item 3g1o4tphv13@google.com (O&O Sectormeeting | An Autumn afternoon with R&E): mailto:[[SOMEONEELSE]]@[[MYDOMAIN]] calItemBase.js:631
Calendar: [calICSCalendar] Parsing ICS succeeded for file:///home/[[ME]]/mycalfolder/NatG.ics CalICSCalendar.sys.mjs:412
Calendar: [CalMetronome] Scheduling one-off event in 364ms CalMetronome.jsm:102
Calendar: [CalMetronome] Starting repeating events CalMetronome.jsm:107
Assert failed: Calendar manager initialised calendars before loadCalendarComponent ran on the first 3pane window. This should not happen.
calUtils.jsm:130:15
Calendar: Start loading of locale dependent preference default values... calendar-chrome-startup.js:248
Calendar: Loading of locale sensitive preference default values completed. calendar-chrome-startup.js:268
@kewisch I added a debug log, yesterday (see above in this thread). The bot that closed this thread says "please re-open this issue" but I don't have permissions to do that. (The bot's comment should perhaps be altered?) I could alternatively file a new issue, but I hope that "@ ing" you is OK
Describe the problem and steps to reproduce it:
Curiously, if I remove the calendar from TB and re-subscribe, the up-to-date calendar DOES appear, and I didn't even need to authenticate (the credentials seem to be successfully stored somewhere).
Anything else we should know?
Thunderbird 115 on Ubuntu 20.04
I looked through old issues. #604 seems similar, perhaps even the same, even though that one was inconclusive.
When I press "Synchronise" this is the debug log output (I have censored my account id):
When I restart my Thunderbird, I get a LOT of output in the debug log (lots of blurb about the content of ical events), but then the very final message is an error:
Earlier on in the debug log I can find one other error: