Summary: | Import of ics files fails | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Andreas <hohenegger> |
Component: | import/export | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | gjditchfield, kfunk, smartins |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | The .ics file for which korganizer does not create events |
Description
Andreas
2013-06-16 16:54:43 UTC
Which kde version do you have ? KDE version 4.10.3. Still can't import *some* .ics files in Korganizer 5.3.1. I'll attach one of those files I can't import. Created attachment 100328 [details] The .ics file for which korganizer does not create events I *manually* added a "UID: ..." line (to work-around https://bugs.kde.org/show_bug.cgi?id=339726). Importing this .ics file then still does not create events despite stating "imported successfully". (In reply to Kevin Funk from comment #4) Kevin, the events in the ICS file have ATTENDEE properties. At the time, was the attendee address one of your mail identities? If so, this is probably the same problem as bug 436812. KOrganizer does not display the events, but akonadiconsole shows that the events have been imported into the calendar. Andreas (if you are still receiving mail about this bug, and if so thank you for your patience), how likely is it that you were listed as an ATTENDEE in your ICS file? This can happen when someone creates an event in their calendar program, and mails you an ICS file to invite you to the event. Nice to see that someone takes these bugs seriously after so long time. I can unfortunately not reproduce this (or rather produce the ics) after so long time. While still using korganizer, I do not recall seeing the issue in recent years. After all this time, if the problem wasn't the "ATTENDEE" bug, we have no hope of tracking it down. *** This bug has been marked as a duplicate of bug 436812 *** |