Version: 1.5.0 (using KDE 3.4.0,%20Mandrake%20Linux%20Cooker%20i586%20-%20Cooker) Compiler: gcc%20version%203.4.1%20(Mandrakelinux%2010.1%203.4.1-4mdk) OS: Linux%20(i686)%20release%202.6.11-6mdk karm should be more informative when it fails to save it's ics file. Currently I can't resolve this problem and karm thus becommes unusable. Also, a popup should show up, this error is too serios to go unnoticed. The only feature karm is providing is gone.
On Suse 9.1 with KDE 3.4 and karm 1.5.1 I get the same notification box: "Error storing new task. Your changes were not saved." on any attempt to create a task. KArm cannot be used.
On Fri, Jun 17, 2005 at 11:40:21AM -0000, J.Frans Hommes wrote: > On Suse 9.1 with KDE 3.4 and karm 1.5.1 I get the same notification > box: "Error storing new task. Your changes were not saved." on any > attempt to create a task. Is this a local file or a remote file? Are there any file permission issues with the file; for example, can you edit with a text editor? Thanks for the report! m
Hi m, We have our home dir's mounted by NIS, so the default ~/.kde/share/apps/karm/karm.ics is a remote. Can edit the file but I do not know how to speak 'calandrian' :) I also set world permissions to rw, but no change in behaviour. When I switch to a local file, karm is OK, so it has some relation with the mounted home diretory. Will use this workaround, but would appreciate a fix, because this is not the only machine I work on and syncing the *.ics by hand ......... Thanks for the prompt reply F On Friday 17 June 2005 14:32, Mark Bucciarelli wrote: [bugs.kde.org quoted mail]
On Fri, Jun 17, 2005 at 02:12:23PM -0000, J.Frans Hommes wrote: > We have our home dir's mounted by NIS, so the default > ~/.kde/share/apps/karm/karm.ics is a remote. Could you check if a stale lock is causing the problem? It would be a ".lock" file in ~/.kde/share/apps/kabc/lock/ Close karm and if there is still a lock file associated with the ics file name, then delete the lock file, and then see if karm now works with that file. m
That has done the trick. Thanks again, I think it would help to place this 'lockfile hint' in the manual or, for the impatient users, in the message box. This was after all what the the original bug submitter asked. One last question on the mechanics of the lock files. I also use Kontact with integrated calendar and 'to do list' on a daily basis. Does KArm peacefully coexists with the suite and its lock files ? F On Friday 17 June 2005 16:34, Mark Bucciarelli wrote: [bugs.kde.org quoted mail]
> That has done the trick. Good. > Thanks again, I think it would help to place this 'lockfile hint' in > the manual or, for the impatient users, in the message box. This was > after all what the the original bug submitter asked. Agreed--I'll leave the bug open until this get's done. > One last question on the mechanics of the lock files. I also use > Kontact with integrated calendar and 'to do list' on a daily basis. > Does KArm peacefully coexists with the suite and its lock files ? Within one user it should. (The lock files are currently stored under the user's home directory.) m
>> Thanks again, I think it would help to place this 'lockfile hint' in >> the manual or, for the impatient users, in the message box. This was >> after all what the the original bug submitter asked. there are only impatient users - at least I am. I am even so impatient that I would like karm to heal itself...
*** Bug 99915 has been marked as a duplicate of this bug. ***
SVN commit 431161 by tstaerk: remind the user of stale locks in case of save problems BUGS:106737 M +1 -1 taskview.cpp --- trunk/KDE/kdepim/karm/taskview.cpp #431160:431161 @@ -476,7 +476,7 @@ if ( uid.isNull() ) { KMessageBox::error( 0, i18n( - "Error storing new task. Your changes were not saved." ) ); + "Error storing new task. Your changes were not saved. Make sure you can edit your iCalendar file. Also quit all applications using this file and remove any lock file related to its name from ~/.kde/share/apps/kabc/lock/ " ) ); } delete dialog;
I have the 4:3.5.5.dfsg.1-4 karm debian package and unfortunately found that this problem is still present. I can see the code in the subversion branch and also the commit log, but have not noticed for some months that karm wasn't useful. I wonder why this still happens. This has been a very very deceiving piece of news. Sorry if I'm been too rude, but I've lost a lot of effort with this. I still like karm but will really like it when this feature does work.
Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343864 please reopen
Hello, this is to say that altought I reported the problem still existed on 3.5.5 I haven't checked that on 3.5.6 so I think it's better to someone to verify the problem still exists on 3.5.6 before reopening.
I just encountered this problem on 3.5.6.
Mmm, I think this _is_ working now, could anyone confirm? Thanks.