401192 - Mini Calendar October 29 - November 4 selects previous day

Status: VERIFIED DUPLICATE of bug 400318

(Calendar :: Calendar Frontend, defect)

Description

[Benny Hill]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8
Build Identifier: 2007102303

If I click on any day between October 29 and November 4 (inclusive) in the mini calendar in the upper left-hand corner, the previous day is highlighted in both the mini and main calendar. So if I click on October 29 in the mini calendar, October 28 is selected.

Reproducible: Always

Steps to Reproduce:
1. Start Thunderbird
2. Click on Calendar icon to activate Lightning
3. Click on any date between October 29, 2007 and November 4, 2007
Actual Results:  
Instead of highlighting the date I selected, it highlights the previous date.

Expected Results:  
It should highlight the date I actually selected.

kubuntu 7.10, Thunderbird 2.0.0.6 (build 20070728), Lightning 0.7 (build 2007102303)

Comment 1

[Benny Hill]

Whenever I attempt to add an event to any of these affected dates, the time is changed from what I select to two hours earlier.  For instance, if I attempt to add an event on October 30th from 15:30 to 16:00, Lightning will change the 15:30 to 1:30 PM and the 16:00 to 2:00 PM.

Even more interesting, as I ALT+TAB back and forth between my browser where I'm entering this bug report and the event popup window, the begin and end times change. It appears the begin time is alternating between 1:30 AM and 7:30 AM.

It is impossible for me to enter an event at the correct time for any date between October 29, 2007 and November 4, 2007.

Comment 2

[Stefan Sitter [:ssitter]]

You need to specify the same timezone in Lightning as in your OS otherwise you will get this known issue (Bug 400318).

In your case I guess it's because of different Daylight Saving Time end dates. What timezone have you configured?

Comment 3

[Benny Hill]

You appear to be correct Stefan. My OS was set to America/Atikokan while Lightning was set to America/Cancun.  Changing my OS timezone settings to America/Cancun appears to have corrected the problem.

Thank you for your comment, I never would have guessed this to be the problem.  My apologies to all who received e-mails about this duplicate bug report.