After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 417475 - Evolution Mail: Evolution does not seem ...
Evolution Mail: Evolution does not seem ...
Status: RESOLVED DUPLICATE of bug 417461
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-12 14:26 UTC by abundy16
Modified: 2007-03-13 21:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description abundy16 2007-03-12 14:26:51 UTC
What were you doing when the application crashed?
Evolution does not seem to account for new daylight savings time in the calendar app. The 'red line' indicating current time on the schedule is an hour behind. 
My system time has updated correctly with the new change. Both system and evolution are set to the same time zone with DST enabled. System time is correct 'red line' time is an hour behind system.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0
Comment 1 jslavin 2007-03-12 16:05:20 UTC
I can confirm that this is true for me as well.  Reminders are popping up at the non-DST time.
Distribution: Fedora Core 5
Gnome Release: 2.14.3
Evolution version: 2.6.3
evolution-data-server version: 1.6.3
Comment 2 jslavin 2007-03-13 14:29:21 UTC
This bug is a duplicate of bug 417461.  If you look at the discussion under that bug, there is a description of how to fix this by editing a (text) file under /usr/share/evolution-data-server-1.6/zoneinfo/...  -- the .ics file that is appropriate for your timezone.  In my case I just needed to replace the line:
RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU
in /usr/share/evolution-data-server-1.6/zoneinfo/America/New_York.ics with
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
This seems like it should be a very simple bug to fix (in a more general way), though to do it really right might require a little more work so that old messages/appointments reflect the correct DST for their year.
Comment 3 André Klapper 2007-03-13 21:27:14 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 417461 ***