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 540676 - historic and some future calendar events not shown at the right time
historic and some future calendar events not shown at the right time
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 562025 (view as bug list)
Depends on:
Blocks: 528902
 
 
Reported: 2008-06-28 20:58 UTC by Patrick Ohly
Modified: 2021-05-19 11:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Patrick Ohly 2008-06-28 20:58:54 UTC
As discussed as part of bug #528902, currently Evolution uses just the information about the summer saving changes that fall into the next 365 days. As an example how that can be wrong, imaging the situation in the US in June 2006: the rules for spring 2007 would be applied to spring 2006, which would be wrong because the rules changed. The same happens for events very far in the future.

Extending libical's system time zone to VTIMEZONE conversion is necessary. In order to preserve compatibility with other programs care must be taken to not export such complete VTIMEZONE definitions. This includes meeting invitations sent by Evolution itself as well as programs like SyncEvolution, which uses e_cal_get_component_as_string() to format an event including its time zone definitions.

Assigning to Suman because according to Chenthill he's the one who can work on this.
Comment 1 Patrick Ohly 2009-01-20 15:03:12 UTC
*** Bug 562025 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2021-05-19 11:04:15 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/

Thank you for your understanding and your help.