Bug 152924 - KOrganizers recurrance doesn't work quite right
Summary: KOrganizers recurrance doesn't work quite right
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-26 14:49 UTC by Tim
Modified: 2017-01-07 22:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim 2007-11-26 14:49:19 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs
Compiler:          gcc-4.1.2 
OS:                Linux

I'm seeing this with kdepim-3.5.8 and there's an outside chance this is
just evolution not understanding kdepims format, but alas here's the issue.

Schedule a recurring meeting for a day/time and invite someone for which the
meeting will actually fall on a different day (i.e. a 6:00 Brisbane meeting will
be 16:00 the previous day in RDU)  Send out the meeting request and it will look
like this:

RRULE:FREQ=WEEKLY;BYDAY=TU
DTSTART:20070430T200000Z
DTEND:20070430T210000Z

Accepting this meeting in evolution will result in an entry being made for 16:00
on 4/30 (a Monday, which is totally correct) but you'll also get an entry for
5/1 (Tuesday) at 16:00 and every Tuesday from then on will get a 16:00 meeting.
 I suspect the cause of the problem is the fact that the invite has the start
and end times in zulu, but the BYDAY designator is in local time for the meeting
scheduler (which in this case was Brisbane.)  Contrast this with evolution's
handling of the same meeting . . . evolution lists the start, end and repeat day
in local time of the scheduler.
Comment 1 Denis Kurz 2016-09-24 18:53:46 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:06:19 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.