Version: (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux While reading an ics file containing the following VEVENT, korganizer eats up all memory of the machine and crashes. !! Notice the invalid DTEND date, causing this !! Another bug was posted (#140022) about failures during writing. This bad entry was generated by korganizer one day. BEGIN:VEVENT DTSTAMP:20070113T195519Z ORGANIZER;CN=Reminder:MAILTO:xxx@yyy.zz CREATED:20061212T202358Z UID:libkcal-260858263.762 SEQUENCE:0 LAST-MODIFIED:20061220T171038Z SUMMARY:Meeting CLASS:PUBLIC PRIORITY:5 DTSTART;VALUE=DATE:20061220 DTEND;VALUE=DATE:20067221 TRANSP:OPAQUE END:VEVENT
Am Mit J
I tested in the soon-to-be-released 3.5.6 KOrganizer didn't crash. but it did cause all the dates in the date navigator to become bold, from 2006-12-20 forward in time. KOrganizer also took a few seconds to load a 1 event .ics file.. so it was definitely thinking hard about something :)
It may not be exactly the same problem, but this one is related: an ics file entry that causes korganizer to fail to launch on starting up. Ironically, this item was marked as "done". Deleting this one entry from the std.ics file fixed the problem. This entry must have been corrupted by korganizer, as no other program was being used to edit the file. Kubuntu Edgy Eft, korganizer 3.5.5 BEGIN:VTODO DTSTAMP:20070225T204641Z ORGANIZER;CN=Ieva Swanson:MAILTO:i-swan@earthlink.net COMMENT:NoStartDate CREATED:20070210T203547Z UID:libkcal-1527311587.656 SEQUENCE:3 LAST-MODIFIED:20070225T202145Z DESCRIPTION:Registration day is 2/20. Plan to get up extra early!! SUMMARY:web: register C.A. camps CLASS:PUBLIC PRIORITY:5 RRULE:FREQ=DAILY;UNTIL=20070220 DUE;VALUE=DATE:20070219 DTSTART;VALUE=DATE:29350930228 COMPLETED:20070225T202145Z PERCENT-COMPLETE:100 RECURRENCE-ID:20070220T060000Z END:VTODO
For the record, I tested with the Henning's bad event and when I went from agenda into month view my system completely hung. We must be missing a check for an invalid end date someplace. Tim Holy's bad to-do works ok in KDE 3.5.6 and above.
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
Created attachment 30003 [details] Test file I've the same problem with korganizer 3.5.9 with the attached ics file. If the DTEND date is wrong, korganizer eats all memory, until the linux system is frozen.
This is working well with KOrganizer 4.2 and libical-0.42, I couldn't reproduce any hang, and the event is properly shown (with end=start). Anyone wants to retest or should we close this?
Closg(In reply to comment #7) > This is working well with KOrganizer 4.2 and libical-0.42, I couldn't reproduce > any hang, and the event is properly shown (with end=start). > > Anyone wants to retest or should we close this? Closing then, the problem is gone.