Evo shifts meeting requests from others by 1 hour

if you have run all your updates and are sure your clock is set to the correct time zone i suggest synch with a time server and synching the system and hardwareclocks

sudo ntpdate ntp-1.mcs.anl.gov
sudo hwclock --systohc

Checked my system time and timezone (thru System|Administration|Time and Date)
Checked my Evo time and timezone (thru Edit|Preferences|Calandars and Tasks|Time Zone)
All updates have been run. tzdata is at 2008a-0ubunbu0.7.10
System syncs daily with pool.ntp.org. I resynced manually to make sure
Ran hwclock as advised
Restarted system

Colleague sent me a test meeting request and it was still shifted forward 1 hour.

Any other ideas?

Followup. I am unclear how the "Adjust for daylight savings time" check box is intended to work. It does not appear to be documented in user documentation.

When I unselect the checkbox, all appointments and meetings, including the ones I create, shift back 1 hour. This makes my appointments wrong and the meeting requests sent to me correct. Unchecking it does the opposite.

I am not sure what I expected, but everything moving globally isn't it.

One more thing. When I receive a meeting request, it is time shifted, but when I send one to the same people, it is not shifted on their computers. That makes me think this is a bug. ??

are you sure your time zome is correct? By this I mean be sure to use the city closest to you in your timezone. Tzdata is known to be wrong from time to time, but there is also the issue that if you are not careful you can set your time zone to someplace you would think is right but is not- some places do not follow DST and others have different start/end rules. I've run across this in the Ubuntu Community Forums in the recent past where a users time issues were caused by this exact issue.

Well, I have tz in Evolution and Ubuntu both set to America/New_York. ( In the windows environment, we use America/Eastern.) I have tried both set to America/Indianapolis, which is where my business is, but Indy, and in fact the whole state, has traditionally had DST issues (some years on, some off) and I don't if they are fixed in tzdata. In any event, the behavior did not change, so I went back to New_York.

In Ubuntu I set the TZ through System|Administration|Time and Date. The TZ is America/New_York and the configuration is set to Manual. I use Manual because this is a laptop and I don't like it hanging when it tries to connect to an ntp server when I don't happen to be on line.

Tzdata is compiled, I think. Is there a way for me to see what is actually in it?

OK Now that first Sunday in April has past, all is well again. I am thinking that the DST start date is wrong in the tzdata file, but ...