Version: (using KDE 4.2.1) OS: Linux Installed from: Gentoo Packages History: First I thought this was either Bug 144132 or Bug 184628, but when trying to work around it by writing new vCal files in KOrganizer from KDE 4.2.1 (instead of just using those from 3.5), I've stumbled upon this. So I'm posting it as a separate bug. Steps of Reproduction: 1) Remove from Kontact/KOrganizer all '.ics' files that were made in KDE3. 2) Close Kontact/KOrganizer and 'killall korgac'. 3) Remove all '~/.kde4/share/apps/korganizer/*.ics' and'~/.kde4/share/apps/korganizer/*.ics~' just to be sure. 4) Start KOrganizer and start writing a new calendar with some recurring events. 5) Save it. 6) Copy the calendar file and use that copy in Kontact as a calendar resource. 7) Check no 1. —> OK (see below) 8) Wait for a day (had my laptop suspended) and/or add/edit an entry. (I'm not completely sure which of the two triggered the bug.) 9) Check no. 2 —> Bug (see below) Results: *) Recurring events do not show up anymore in KOrganizer (they still do in the Planner though). *) In the file the PRODID field changes. (see "Checks" below) *) In the file the DTSTAMP and LAST-MODIFIED fields change. Expected Results: *) Not messing up the calendars would be just fine, thank you :) Checks: The checks mentioned are a simple 'ack PRODID *.ics' (grep would work as well, but I like 'ack' better) to show which version the files claim to be. Check no. 1 output: PRODID:-//K Desktop Environment//NONSGML KOrganizer 4.2.1//EN Check no. 2 output: PRODID:-//K Desktop Environment//NONSGML libkcal 3.5//EN
Created attachment 32639 [details] Original file (check no. 1) A vCal file as I wrote it with KOrganizer 4.2.1 and backed up just after it passed Check no. 1 as described in the bug description. This version of the file works as expected.
Created attachment 32640 [details] Buggy file (check no. 2) File as it was the next day, when I noticed the bug and tested it with Check no. 2 that it failed. This version of the file had to be modified by KOrganizer/Kontact itself, since I had made no changes or additions to *this* file since the Check no. 1.
The PRODID change might have been triggered by the fact that I imported those files as vCal (instead of iCal). I'm trying to reproduce the bug if I import the calendars as iCal (which they are). I'll give it a week or two: if nothing happens, I'm closing this bug.
Created attachment 32646 [details] Diff from the buggy file to the original (check no. 3) After a while the file (this time correctly imported as iCal) changed even though I didn't touch it. All I did was switch from the KOrganizer view to the Overview view (with Planner, Special Dates and New Messages plugins), but I don't think that's related. Changes this time: DTSTAMP, LAST-MODIFIED, DTSTART and PRODID.
Created attachment 32653 [details] Diff from the buggy file to the original (check no. 4, new user) I tried to reproduce the bug using a new user (which I made just to test this). I used two iCal files with recurring events in them: * One (the same that is posted under Attachment 1 [details]) I didn't alter and after 12 hours it stayed as I left it. * The other (a more complicated and personal one, set as primary/default calendar) I was playing around with a bit, moved some events around etc. and a similar bug occured as in Comment #4: it changed PRODID, many DTSTAMP, some LAST-MODIFIED (not all were modified by me!), a few SEQUENCE and EXDATE (not by me!), some DTSTART and DTEND (probably modified by me). See attached diff to the original file.
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.
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.