Please report any other irregularities here.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20090910 Ubuntu/9.04 (jaunty) Shiretoko/3.5.3 Build Identifier: lightning build 2008091718 My university provides software (thanks Matt Gray) for managing conferences, and provides a .ics export link that works nicely with Lightning. Our location is Canberra, Australia, so Matt has set the .ics file to use timezone of "Australia/Canberra". Apparently, most calendar software handles this just fine. For example, it works perfectly with Google Calendar, and I believe Matt tested others as well. With Thunderbird/Lightning, however, since the recent daylight-saving (summer-time) change, events were showing up one hour later than then should have. Matt made some tweaks to his server to work around the bug, so it no longer appears, but it seems that the real solution would be to add "Australia/Canberra" as a legal timezone in conformance with other calendaring software. Reproducible: Always Steps to Reproduce: Matt Gray should be able to provide a failing copy of the calendar in question. Alternatively, I have a copy on my desktop.
Created attachment 405221 [details] .ics file that caused the problem .ics file that produced incorrect results. My GNOME timezone (using Ubuntu 9.04) currently set to Canberra.
Attachment #405221 - Attachment mime type: text/calendar → text/plain
Lightning doesn't define timezones. The built-in timezone support is created from the latest Zoneinfo / Olson timezone database release. Australia/Canberra doesn't exists in this database. The nearest one seems to be Australia/Sydney. From Lightning 1.0pre Australia/Sydney timezone definition: DST starts on first Sunday in October and ends on first Sunday in April From your example Australia/Canberra timezone definition: DST starts on last Sunday in October and ends on last Sunday in March It seems that the timezone definition send by your server is out of date. Looking at <http://www.timeanddate.com/worldclock/timezone.html?n=57> the timezone rules changed back in 2008.
John, is your problem solved or do you have additional information to solve it?
No response for a while now, closing INCOMPLETE. Please reopen if you can reproduce or answer any unanswered questions.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.