Bug 115456

Summary:	Korganizer can no longer save events/todos, pops up "unable to save event" dialog.
Product:	[Applications] korganizer	Reporter:	Al Muckart <silver>
Component:	todoview	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	smartins, Wolfram.R.Sieber
Priority:	NOR
Version First Reported In:	3.4.2
Target Milestone:	---
Platform:	unspecified
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Picture of the dialog saying "unable to save attachment"

Description Al Muckart 2005-11-01 04:21:00 UTC

Version:           3.4.2 (using KDE 3.4.2, compiled sources)
Compiler:          gcc version 3.4.2 [FreeBSD] 20040728
OS:                FreeBSD (i386) release 5.4-STABLE

This sounds like a similar issue to bug #97213, but is defenitely a bug and not a wishlist.

After enabling, testing, and then disabling the exchange plugin in kontact I can no longer save new events or todos in korganizer. I get a dialog saying "new event cannot be saved" which is totally obscure and gives me no help in tracking down WHY the new event cannot be saved.

I have checked that I am using the default korganizer resource and that that std.ics is writeable. I have completely disabled the exchange plugin and the problem persists.

Comment 1 Al Muckart 2005-11-01 05:13:06 UTC

Created attachment 13239 [details]
Picture of the dialog saying "unable to save attachment"

Comment 2 Reinhold Kainhofer 2006-11-02 19:26:34 UTC

Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.

Comment 3 Sergio Martins 2009-01-23 06:20:47 UTC

Can you retest in kde4?

Thanks

Comment 4 Wolfram R. Sieber 2009-06-05 21:40:01 UTC

Bug #122368 describes a similar bug. The issue there apparently is left-over lock files. I posteda workaround and kind of a fix there. Maybe that'd solves your issue: https://bugs.kde.org/show_bug.cgi?id=122368#c5

HTH ... Wolfram

Comment 5 Sergio Martins 2009-06-05 22:36:50 UTC

(In reply to comment #4)
> Bug #122368 describes a similar bug. The issue there apparently is left-over
> lock files. I posted a workaround and kind of a fix there. Maybe that'd solves
> your issue: https://bugs.kde.org/show_bug.cgi?id=122368#c5
> 
> HTH ... Wolfram

Thanks for your solution. I'll mark this one as a dup of #122368 as it's the same error. (the cause can be different but we don't have any news from the reporter since 2005).

*** This bug has been marked as a duplicate of bug 122368 ***