Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 233155 - KOrganizer/Kontact uses out-of-date timezone information
Summary: KOrganizer/Kontact uses out-of-date timezone information
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 6
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-20 18:06 UTC by Rich Ibbotson
Modified: 2008-05-06 19:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:23:19 UTC

Attachments (Terms of Use)

Description Rich Ibbotson 2007-03-20 18:06:57 UTC
Description of problem:
Meeting invitations sent using KOrganizer to Outlook users (or received from
Outlook users) do not reflect the recent change in daylight savings time.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. In Kontact, configure the current time zone to be America/New_York.
2. Have someone using a different calendar program send you a meeting invitation.
3. Accept said invitation using Kontact.
4. Note that the meeting time is one hour later than it is supposed to be.
Actual results:
Meeting invite is imported as if the current time zone is EST.

Expected results:
Meeting invite should be imported using EDT.

Additional info:
I believe this is due to incorrect timezone information in the ics files
installed by kdepim.  There is a very long description of the related libical
problem here: (see, for
example, comment #53)

Note that the file /usr/share/apps/libical/zoneinfo/America/New_York.ics
contains RRULE entries that show daylight savings time as beginning the first
Sunday of April, rather than the second Sunday in March (if I understand the
syntax of this file, that is):


Comment 1 Bug Zapper 2008-04-04 06:36:18 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 2 Bug Zapper 2008-05-06 19:23:18 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.