Version: 4.1.0 with KDE 4.1.1 (using KDE 4.1.1) Compiler: gcc version 4.3.1 (Debian 4.3.1-9) OS: Linux Installed from: Debian testing/unstable Packages Recurring events appear twice at the original created time and day in the weekly view in korganizer. When deleting them they seem to be removed from the weekly view, but not from the monthy overview (days with events are bold font, and days that had only the recurring event are still bold). Also, if the view if changed or updated, the seemingly deleted events reappear. Because of that, recurring events are unusable in korganizer. How to reproduce: 1. Create an event 2. Mark it as recurring, e.g. weekly. After that, the events appears twice in the original time and day. 3. Delete both. They will disappear in the weekly view, but the monthly view has still the bold font. 4. Update the weekly view (click on another week, and then on the original week again). The deleted events reappear. 5. Restart korganizer. The deleted events are gone. Expected behavior: Making an event recurring should show the event only once; deleting an event should really delete it. Tell me if I can help further. Regards, Sten
What type of resource are you using? Can you try with a more recent version of KDE? Thanks
> What type of resource are you using? I am using the standard calender resource. > Can you try with a more recent version of KDE? I am running Korganizer 4.1.0 on KDE 4.1.3 since some time, and I am unable to reproduce events appearing twice. This seems to be fixed. But the date navigator (on the left side) is still not updated correctly. If there's no event, the day should be written using normal fonts, if there are events, in bold. After deleting the recurring test-event, the weekly view is updated correctly, but the date navigator still shows bold-font days where the recurring event was. Regards, Sten
> This seems to be fixed. I agree. > After deleting the recurring test-event, the weekly view is updated correctly, > but the date navigator still shows bold-font days where the recurring event was. That's true, and there's already an open bug on this issue. Thanks for the quick response!