Version: 3.2 (using KDE 3.2 BRANCH >= 20040204, Mandrake Linux Cooker i586 - Cooker) Compiler: gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk) OS: Linux (i686) release 2.6.3-16jwc01 Here's how I observed the problem. I created an event which spanned two days, eg: Start 8 Sep 2004 08:00 End 9 Sep 2004 14:00 Then I enabled recurrence, recurring every 6 months, on the second Wednesday of the month. After completing this event entry, I scrolled to where the first recurrence should be (9 Mar 2005) and found that the day was highlighted on the month view in the mini calendar in the top-left of the Kontact window, but no event was visible in the day view (RHS). Reducing the period of the event so that it does not cross a day boundary (midnight) caused the event to recur correctly. Neither does this problem seem to occur for multi-day events without an associated time. I'm sure many people (like me) will want to schedule recurring multi-day events, so thanks in advance for fixing it. Kontact is GREAT!
*** This bug has been marked as a duplicate of 42899 ***
looking back on the previous (RESOLVED) duplicated bug, it appears that the resolving was done by saying that it won't work for overnight appointments rather than actually fixing it. Maybe it was fixed, but has happened again because of the new upgrades, I'm not sure. To recap the problem is that recurring events (like my night shifts) are not being shown in the future. Old appointments (made before my new version of kontact/korganiser) work correctly still, it's only the new shifts which I've had to change to which don't work (making me guess this is a problem with the way the appointment is stored in the ical format) I do hope this can be fixed in the near future. Kontact really is pretty good though!
Am Sonntag, 30. Oktober 2005 15:18 schrieb stu.young@zoom.co.uk: > looking back on the previous (RESOLVED) duplicated bug, it appears that the > resolving was done by saying that it won't work for overnight appointments No, the bug report was closed as a duplicate, since bug #42899 is the same problem. That bug report is still open, so don't worry about this. It's just that we don't have enough time to fix all the bugs :-((( Cheers, Reinhold