Evolution does not recognize daylight saving time

Bug #147710 reported by tombraun
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

This is on Ubuntu 7.04, with Evolution 2.10.1 and Gnome 2.18.1.

I am located in New Zealand and work with people in California. When I need to schedule a reminder for a conference call with them, I just create the calendar event in their time zone (using the timezone field in the dialog for the event creation). Normally, this all works wonderfully and Evolution translates this time into a proper time for my local timezone.

However, last weekend we switched to daylight saving time in New Zealand. My system time was properly updated, the clock/calendar applet on the desktop displayed the time correctly. Using programs like gworldclock I can see that my system also knows the correct time in California. But when I now create an event in Evolution in California time, it displays its start in NZDT one hour early.

If I look at the event in the clock applet, the time of the event is shown correctly.

Clicking the 'adjust for daylight saving time' check box in Evolution's preferences doesn't make any difference.

Finally, I noticed that Evolution still thinks my time zone is UTC+12. But with the start of daylight saving time here, it is actually UTC+13...

This is an important feature for me to work, so any help with this is greatly appreciated. If this is fixed for Ubuntu 7.10 then I would be happy with it as well, because I will probably upgrade soon, but it would be good to know.

Revision history for this message
tombraun (tombraun) wrote :

Alarm and notification seems to be correct, though. The problem appears to be with the display code for the calendar.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, I haven't seen this problem in the past, with the change to daylight saving time in my country (Chile) evolution recognized the change and update it, not confirming. Please after upgrade to Gutsy follow up in this report so we can know if that was fixed for you.

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.