Bug 138491 - recurring events are missing when kontact is restarted
Summary: recurring events are missing when kontact is restarted
Status: RESOLVED FIXED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-07 10:00 UTC by Robert
Modified: 2007-07-19 17:15 UTC (History)
0 users

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 Robert 2006-12-07 10:00:19 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I've set up a recurring event (every M W F). If I restart Kontact, the event doesn't show up on the calendar, due to the "start date" showing as being after the "begin date". This behavior occurs on every recurring event I've tried to set up, and returns upon restart if the event is recreated.

Note, the event does show up on the summary page, but is missing from the calendar.
Comment 1 Michael Sims 2006-12-21 21:27:35 UTC
I can confirm this occurs for me too (KDE 3.5.5).  KDE seems to alter the 'start date' of recurring events to be somewhere approximately six weeks or so after the 'end date'.  It does this on restarting Kontact, or on a reminder for the event being triggered.  Once this has been done, the event is pretty much invalid, since the 'start date' is now weeks after the 'end date', and the event is no longer displayed in most views of the calendar.

Suspect you have a simple bug somewhere where calculating the display of recurring events (i.e., bolded dates on the two-month lookahead calendar pane on the left side of the screen) is causing the 'start date' of the event to be altered.  There's an '=' instead of an '==' somewhere.

Reproduce: Create an event.  Set it to recur, weekly, or every two weeks or somesuch.  Close Kontact and reopen, or set a reminder and let it fire, or just page around in the Calendar display - seems to be occur easily.  Once the event disappears, find it again using the 'List' view (it won't show on other views of your calendar, since the date range is invalid).  Examine the start and end dates of the event.
Comment 2 Bram Schoenmakers 2006-12-21 21:30:47 UTC
Dupe of bug 136221?
Comment 3 Reinhold Kainhofer 2007-01-04 15:03:12 UTC
Thanks for the bug report. Unfortunately I can't reproduce the problem.


Do you use the standard file resource?
If so, can you please look into the std.ics file and copy the BEGIN:VEVENT...END:VEVENT block for that event to this report (together with the exact settings that you used for creating the event).

Are you on a 32 or a 64-bit platform? Any other changes to the settings (that might or might not be relevant)?


Cheers,
Reinhold
Comment 4 Tilo Klausing 2007-01-08 15:58:49 UTC
Hi,
I can confirm this Bug.

Scenario:
I have several appointments that get messed up by kontact (standalone korganizer does not show this behavior). I fix it, it gets stored in the file like that (thats how it should look like):

BEGIN:VEVENT
DTSTAMP:20070108T143810Z
ORGANIZER;CN=Tilo Klausing:MAILTO:x@y.z
CREATED:20061127T091854Z
UID:libkcal-653224037.492
SEQUENCE:16
LAST-MODIFIED:20070108T143809Z
SUMMARY:Scrubs
CLASS:PUBLIC
PRIORITY:5
CATEGORIES:TV
RRULE:FREQ=WEEKLY;COUNT=22;BYDAY=FR
EXDATE;VALUE=DATE:20061229
DTSTART:20061215T090000Z
DTEND:20061215T093000Z
TRANSP:OPAQUE
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:PT0S
END:VALARM

END:VEVENT

After restarting Kontact, the event looks like this:

BEGIN:VEVENT
DTSTAMP:20070108T144222Z
ORGANIZER;CN=Tilo Klausing:MAILTO:x@y.z
CREATED:20061127T091854Z
UID:libkcal-653224037.492
SEQUENCE:16
LAST-MODIFIED:20070108T144214Z
SUMMARY:Scrubs
CLASS:PUBLIC
PRIORITY:5
CATEGORIES:TV
RRULE:FREQ=WEEKLY;COUNT=22;BYDAY=FR
EXDATE;VALUE=DATE:20061229
DTSTART:20070202T090000Z
DTEND:20061215T093000Z
TRANSP:OPAQUE
BEGIN:VALARM
DESCRIPTION:
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:PT0S
END:VALARM

END:VEVENT

Notice the changed start date. I played around a bit and noticed something. If I turn off the calendar component of the Kontact overview page, the fixed appointment remains unchanged. So somehow the overview component, that displays upcoming events, changes the Events.

I hope you are able to pin down this Bug, because it is pretty annoying, my workaround for now is turning off the calendar view in the kontact overview, but that's only to be able to use it at all.
Comment 5 Robert 2007-01-14 18:29:52 UTC
The problem is DTSTART DTEND

I've created an event Monday, MO,WE,FR

Since 15/01/2007 Until 26/01/2007

BEGIN:VEVENT
DTSTAMP:20070114T172603Z
ORGANIZER;CN=********* :MAILTO:**************
CREATED:20070114T172351Z
UID:libkcal-190374433.533
SEQUENCE:0
LAST-MODIFIED:20070114T172554Z
SUMMARY:test
CLASS:PUBLIC
PRIORITY:5
RRULE:FREQ=WEEKLY;COUNT=6;BYDAY=MO,WE,FR
DTSTART:20070119T090000Z
DTEND:20070115T110000Z
TRANSP:OPAQUE
END:VEVENT
Comment 6 chris-kde 2007-02-20 23:41:24 UTC
I can confirm I'm seeing the same problem with Kontact 3.5.5 under Kubuntu Edgy (6.10).
I can also confirm the workaround of disabling the Calendar in the summary.

Interestingly, when Calender is enabled in Summary, if I am in the Calender view, I can click on the event, adjust it's end date, and I will see it fixed, and then if I click on the day of the event, the event disappears.
If I have the Calendar disabled in the summary than this doesn't occur, even though I never view the summary.

I've got two events where I saw this occur so far - it probably would effect others if they came within the range of the summary view.
The details for the events I created were:
Start Date: 17 Feb 2007, 16:30
End Date: 17 Feb 2007, 18:30
recurrence is weekly for 3 occurrences
This event's end time gets changed to 24 Feb 2007

The other event is
Start Date: 23 Feb 2007 20:00
End Date: 23 Feb 2007 22:00
recurrence is daily for 2 occurrences
This event's end date gets changed to 25 Feb 2007

My Calendar summary view is configured to look 5 days ahead.
Comment 7 Bram Schoenmakers 2007-05-15 12:44:20 UTC
Is still valid in KDE 3.5.6 (or in the new 3.5.7 to be released in a few days)? There's a change this has been fixed in 3.5.6.
Comment 8 chris-kde 2007-07-19 07:36:04 UTC
I encountered this problem on 3.5.5 and have just upgraded to 3.5.6. The problem appears to be solved for me on 3.5.6 (using Kubuntu Feisty 7.04)
Comment 9 Thomas McGuire 2007-07-19 17:15:28 UTC
>The problem appears to be solved for me on 3.5.6
OK, closing this report.
If anyone can still reproduce with 3.5.6 or higher, please leave a comment or reopen.