Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages STEPS TO REPRODUCE: 1. Start korganizer and select the single-day view. 2. Create a new event starting on Mar 1 2009 at noon and recurring daily. 3. Browse to March 8, 2009, and observe the 8th occurrence of the event from (2). 4. Right-click this occurrence, and select "Disassociate this occurence". 5. There are now two events displayed at noon; one is selected and is the original recurring event; the other is the new disassociated event. 6. Browsing to another date and then back to March 8, the original recurring event can no longer be seen. ACTUAL BEHAVIOR: Two copies of the event are seen after selecting "disassociate this occurrence". EXPECTED BEHAVIOR: Only one event is displayed after "disassociate this occurrence"; namely, the disassociated occurrence. OTHER NOTES: It appears that data associated with the recurring event is correctly updated; the disassociated date appears in the exception list of that event even if it is double-clicked directly after step 5 above. It appears that simply the page is drawn after the creation of the new event but before the recurring event is revised. This was observed using korganizer package 4:4.2.0-0ubuntu1-intrepid3.
I can't reproduce this with KDE 4.2.1. or current trunk. Can you reproduce this every time? If it's created at another time besides noon, does it work? Does it happen in week view?
Sergio, Thanks for the quick reply. - I am able to reproduce it every time, even on a virgin calendar. - It happens for any date, time, recurrence, time zone, or recurrence rule. - It does happen in week view.
Week view and day view are the same widget, so that's expected. I don't have a 4.2.0 installation here but I know some fixes were made to agenda view meanwhile. 4.2.1 is around the corner, let's wait and see.
I managed to reproduce and find the cause of this bug while looking at an unrelated issue. When an event is modified an incidenceUpdated() signal should be emited, and this was only happening if you had the "groupware comunication" enabled. Commit r939315 fixed that.