374967 - 2005 DST changes not applying to Outlook meeting requests

Status: RESOLVED WORKSFORME

(Calendar :: Lightning Only, defect)

Description

[Michael Cronenworth]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1) Gecko/20061107 BonEcho/2.0
Build Identifier: Mozilla Thunderbird 1.5.010 with Lightning 0.5pre (20070321)

I am receiving event invitations from an Outlook user. When I open the e-mail in Thunderbird, the event time shows to be "2:00 PM CDT" even though the *real* time for the event is 1:00 PM CDT.

Reproducible: Always

Steps to Reproduce:
1. Receive meeting.ics from Outlook user
2. "When" time is one hour off
3.
Actual Results:  
Shown 2 PM CDT.

Expected Results:  
Shown 1 PM CDT.

If I add the event to my calendar it has the 2PM time. If I change my timezone from Chicago to Denver in Thunderbird settings it will show 1PM on my calendar, but it will not give me the alarm until 2PM (and the alarm shows 1PM when it pops up).

I will attach an example meeting.ics.

Comment 1

[cmtalbert]

Check to be sure that your Timezone is set to America/Chicago.  Lightning still sometimes incorrectly guesses your default timezone as America/Cancun, and Mexico did not follow the US DST change.

Comment 2

[Michael Cronenworth]

Attachment: example meeting.ics

This is the example meeting.ics file. It has a meeting for 1PM to 2PM. I edited the names and emails for privacy purposes, but the rest is left intact.

If I import this it will display 2PM to 3PM on my calendar - set to Chicago timezone.

I forgot to add that this happens on Linux(Fedora Core 6) and Windows XP. Both OSs have the DST patches and have the correct time set.

Comment 3

[Bas van den Bosch]

TZID:(GMT-06.00) Central Time (US & Canada)
DTSTART;TZID="(GMT-06.00) Central Time (US & Canada)":20070322T130000

The problem at first sight seems to be that the timezone in the event has quotes around it, it's not the same as the timezone in the definition, this is a known bug (bug 357252) which however was fixed. The DST-setting in the VTIMEZONE seems correct: standard GMT-6.00, from the first sunday of november till the second sunday of march it's GMT-5.00: http://www.timeanddate.com/worldclock/city.html?n=64

If I set my timezone to chicage and import your event, it shows at 13.00 hours as it should. When I edit it, the time in the eevnt-dialog changes to 19.00 hours as I'm at GMT+1. You are sure your timezone-patches to your OS are applied? Which timezone are you in yourself?

Comment 4

[Michael Cronenworth]

Fedora Core 6 has the DST changes - my time changed correctly last week, and I am using ntp to make sure my time is as correct as it can be. I am in the Central Time Zone. If I do a yum update I have no packages to apply. I have all the patches currently available.

Windows XP also is set to Central. It has the correct time.

Remember, two OSs on two computers have the same "off by 1 hour" issue.

Comment 5

[Michael Cronenworth]

Update -- I received an event from the same Outlook user, this time for April 2nd. It shows the correct time. This would place it in the old DST rule area. It's obviously something with Lightning's DST handling, is it not?

Comment 6

[Bas van den Bosch]

Or this might be due to a foreign timezone definition which was handled in bug 314339 (like in bug 378019) though the difference should be five or six hours then. Added qawanted as I didn't see anyone else claiming this kind of problem. Could you look at your tzdata-file (don't have it myself) to see how the timezone is defined?

Comment 7

[George Gorsline]

Same/similar problem here from within Lightning.  Booked meeting request for 7:30 AM on Oct 31st - displayed in calendar as 8:30.  However, recurring meeting appointment for 6:30PM (bi-weekly) was set from September through to June without an issue across both time change boundaries.  WIN2K SP4, time zone set to Americas/Toronto (ET).  Hope this is helpful.

Comment 8

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Timezones have been updated to 2007k Olson database (2007-12-31) and the code for guessing timezone has been improved.

Does the issue still occur in the latest 0.8pre nightlies?

Comment 9

[Michael Cronenworth]

I believe this issue was resolved in 0.8. During my time using 0.8 I never ran into DST issues. I'm using 0.9rc2 now and everything still looks good.

Comment 10

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

-> WFM. Fixed is used for bugs with known patches.
https://bugzilla.mozilla.org/page.cgi?id=fields.html#status