Version: (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345325: Suddenly today I am unable to add new todo items in Kontact/KOrganizer. When I try to add a new one, it says, "Sorry: Unable to save ToDo 'name-of-new-todo'." I have tried closing all Kontact/KOrganizer-related processes, and tried logging out and back in: no go. I can delete todos just fine. I don't understand why it suddenly started doing this. I can't find anything on Google or the BTS about it. I discovered that the default resource in Korganizer was set to be an iCalendar file instead of a vCalendar file. But apparently, since it was already a vCal file, Korganizer couldn't handle that it was set to use it as an iCal file. When I changed it back to vCal, it was fine. Well, it's good that it didn't break the file, but it should be able to figure out that it's trying to use the wrong format, and it should ask you to fix it, instead of saying, "Sorry, can't do what you want for some unknown reason."
I've just got the same thing today. I hadn't done any upgrades or anything, just suddenly can't add TODO items or calendar items. I can delete TODO items though, as the original poster noted. I did notice that when I first switched to Calendar view, Kontact paused for about a minute before it would display the calendar. However, I can't work out what the original reporter means about ical/vcal. My calendar is stored in ~/.kde/share/apps/korganizer/std.ics. It appears to be in vcal format, but it always has been -- I've got a backup from 6 months ago which starts "BEGIN:VCALENDAR", just like the file does today.
OK, I have managed to work around it. I have to edit the properties for the resource file (either via Korganiser, or via 'Resources' in the control panel), set it to be vCalendar format, and *also* rename it to be std.vcs instead of std.ics (physically renaming the file at the same time). Then it works again. I have no idea how this bug could suddenly have appeared.
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 kontact (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.