Bug 105122 - Unable to save Event
Summary: Unable to save Event
Status: CONFIRMED
Alias: None
Product: kresources
Classification: Miscellaneous
Component: framework (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 130003 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-05-05 01:40 UTC by Michael Corsa
Modified: 2009-06-05 21:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Corsa 2005-05-05 01:40:16 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

This started after a new install of SuSE 9.3 with KDE 3.4.  I copied over my prior .ics Calendar file which had been used under SuSE 9.2 with KDE 3.3.4 successfully.  Whenever I now try to save a new calendar event I receive the message "Unable to save Event . with the Event name.  I have checked the permissions and user/group on the calendar file and all appears correct.
Comment 1 Jan Erik Hiim 2005-05-05 14:04:05 UTC
Same happened to me, I cant not delete events I saved before I updated to KDE 3.4
Comment 2 Mr Ter 2005-05-29 10:17:52 UTC
I have the same problem with ToDo
Comment 3 Jan Sielemann 2005-06-02 18:32:19 UTC
I have the same problem (Unable to save Event), when i'm trying to create an new event on my "Calender on IMAP Server via KMail". Editing and deleting works properly. Btw: sometimes my Entries are lost....no idea, why!
Comment 4 LeRoy DeVries 2005-08-04 19:15:41 UTC
I am also using SUSE 9.3 /w KDE 3.4.2 and unable to save new event
Comment 5 gwydion 2005-08-08 10:40:43 UTC
Since the update from KDE 3.4.1 to 3.4.2 (Kubuntu) I have the same problem, too. I cannot save an event to a local calender file. Deleting the calendar from the list and reopening it (creating a new calendar entry from this file) resolves the problem temporarily.
Comment 6 Chuck Coxhead 2005-08-14 17:33:35 UTC
Ditto. It was working fine and now I can't enter any new events.  Using Standard iCal.  Permissions OK.  Also configured to use KPilot with Standard calendar.
PCLinux RPMs
KDE 3.4.2
Korganizer 3.4.2
Kontact 1.1.2
Comment 7 Chuck Coxhead 2005-08-14 17:46:36 UTC
Follow up to my previous comment.  I added a vCal Resource and I am able to add events to that.  I also tried adding an additional iCal.  I can add events to that.  I tried exporting the std.ics to another ical and I could not add to that.  All of these experiments were done with "Be ask which resource to use" for New Events/To Dos.
Comment 8 Tobias Koenig 2005-08-16 19:54:21 UTC
Hi,

here were posted several _different_ bugs....

1) Can't save events on IMAP:
  That has been fixed in current version from 3.5 branch

2) Can't save/create events after update to XXX
Make sure your calendar/addressbook is setup correctly and points to a valid file/directory.

I can save events, tasks and contacts with a fresh build, so it must be a configuration problem on your side.

Ciao,
Tobias
Comment 9 Chuck Coxhead 2005-08-17 01:30:40 UTC
1) I'm not using IMAP.

2) My address book and calendar are set up correctly and I checked the permissions, as I said in my first comment.

You don't have problem therefore it's not a bug.  Why didn't we just check with you first?  Silly us.

Adios,
Chuck
Comment 10 Thomas Müller 2006-04-13 14:33:12 UTC
I have kde 3.4.2 and am not able to update :-(
When i enter a new event, i get the "Unable to save event" error, but the event is saved. I can edit events without errors.

Same for todos, when i create them, i get the error (but they are created nontheless) but editing works fine.
Comment 11 Thomas Müller 2006-04-13 15:14:05 UTC
Additional information:
Saving Contacts does not show the bug.

The bug is still present in my installation at home with KDE 3.5.2
Same thing, i can create events, get the error "Unable to save event" but it is stored on the imap correctly.
Comment 12 Manuel Koch 2006-10-18 22:00:43 UTC
I have the same problem with KDE 3.5.5 after updating to this recent version. 
Adding new event to local file resource fails with message 'Speichern von Ereignis "test" nicht möglich'.
Resource file's accessable and permissions are ok.
Even the current content of this resource is shown in kontact's calendar. Why should reading resource succeed while writing to fails ?
Comment 13 Will Stephenson 2006-10-30 09:02:14 UTC
*** Bug 130003 has been marked as a duplicate of this bug. ***
Comment 14 Will Stephenson 2006-10-30 09:04:57 UTC
To reporters who have this bug with KDE 3.5.5:  Please try removing the calendar resource that has the bug, and recreating it with the same settings (same path to calendar file). 

Instructions:
1) Quit Kontact and Korganizer
2) Start "kcmshell kresources"
3) Remove the Calendar resource with the problem
4) Recreate it
5) Start Kontact or Korganizer
6) Try to add an event.
Comment 15 Manuel Koch 2006-10-30 18:10:32 UTC
Tried workaround described in comment #14.
1) Removed faulty resource file via kcmshell
2) Creating new standard resource file
3) opening kontact and importing previous resource to standard resource
Afterwards editing/adding of events was possible again.
Why should importing the same data fix the problem ?
Comment 16 Reinhold Kainhofer 2006-11-02 19:02:11 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 17 Mark van Rossum 2007-03-06 22:17:23 UTC
I had the same problem.
   rm ~/.kde/share/apps/kabc/lock/* 
fixed it.
Comment 18 Jan Torben Heuer 2007-03-27 19:03:37 UTC
I have the same problem (Unable to save Event). It went, when I selected "Ask for calender to save" rather than "Use default calender" in the settinigs.

Don't know, why items get lost, although they are shown in the summary...

Jan

Comment 19 Claes 2008-11-07 13:09:03 UTC
I had also same problem, Unable to save Event in KOrganizer

Opensuse 11.0 64bit, kde 4.1.3

Removing everything in ~/.kde4/share/apps/kabc/lock fixed the problem.


Claes
Comment 20 Wolfram R. Sieber 2009-06-05 21:35:36 UTC
The comment #19 hint on lock files was a good hint. I posted my detailled solution on https://bugs.kde.org/show_bug.cgi?id=122368#c5 which avoids corrupting valid locks.