[Korganizer-devel] [Bug 122368] unable to save event / todo

[Wolfram R. Sieber]

https://bugs.kde.org/show_bug.cgi?id=122368


Wolfram R. Sieber <Wolfram.R.Sieber at GMail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Wolfram.R.Sieber at GMail.com




--- Comment #5 from Wolfram R. Sieber <Wolfram R Sieber GMail com>  2009-06-05 21:28:35 ---
The suggest of comment #3 from Richard Bos didn't work for me, however, I've
got one and a half workaround and one half fix for the issue.

The workaround is to open korganizer as usual but then to ignore everything it
offers to you -- as you won't be able to save anything anyway. Instead, use the
file menu, then "Open... (Ctrl+O)", then select std.ics. That is the file the
standard calendar is stored in. Doing so, you actually open the yet opened
default calendar a second time, but for some miracle I do not yet understand,
this second one is writable. So, as a workaround instead of using the calendar
korganizer offers you by default, you re-open that very same calendar and work
there, save when you're done by issuing Ctrl+S. Colors might be messed up in
the second view, but once you save, the other (default) view of the calendar
will be updated, and everything will be okay, including the colors.

At some occasion korganizer told me the reason why it couldn't save the
calendar [the one opened by default] was because some other resource was using
it. Using "ps ax" I couldn't find another korganizer process which might have
been using that very calendar. Using "lsof" didn't point to any program that
had the std.ics file opened. I even rebooted to make sure that there definitely
wouldn't be any other process around that could prevent korganizer from writing
to its own calendar. Though, the "can't save" error didn't go away.

Now, what? "locate std.ics" finally gave the hint:
    box:/home/me# locate std.ics
    /home/me2/.kde/share/apps/korganizer/std.ics
    /home/me2/.kde/share/apps/korganizer/std.ics~
    /home/me/.kde/share/apps/RecentDocuments/std.ics.desktop
   
/home/me/.kde/share/apps/kabc/lock/_home_me_.kde_share_apps_korganizer_std.ics.lock
   
/home/me/.kde/share/apps/kabc/lock/_home_me_.kde_share_apps_korganizer_std.icsmL6FzGpv
    /home/me/.kde/share/apps/korganizer/std.ics
    /home/me/.kde/share/apps/korganizer/std.ics~
    box:/home/me# updatedb
    box:/home/me# ll `locate std.ics`
    -rw-r--r-- 1 me2      me2        3253 19. Mai 14:43
/home/me2/.kde/share/apps/korganizer/std.ics
    -rw-r--r-- 1 me2      me2        2880 19. Mai 14:43
/home/me2/.kde/share/apps/korganizer/std.ics~
    -rw-r--r-- 2 me       me            0  3. Jun 15:20
/home/me/.kde/share/apps/kabc/lock/_home_me_.kde_share_apps_korganizer_std.ics.lock
    -rw-r--r-- 2 me       me            0  3. Jun 15:20
/home/me/.kde/share/apps/kabc/lock/_home_me_.kde_share_apps_korganizer_std.icsmL6FzGpv
    -rw-rw-r-- 1 me       me       229695  5. Jun 20:39
/home/me/.kde/share/apps/korganizer/std.ics
    -rw-rw-r-- 1 me       me       229409  5. Jun 20:39
/home/me/.kde/share/apps/korganizer/std.ics~
    -rw------- 1 me       me          142  5. Jun 20:38
/home/me/.kde/share/apps/RecentDocuments/std.ics.desktop

See those _home_me _.kde_share_apps_korganizer_std.ics* files there? That looks
like lock files. Also, the timestamp -- 3. Jun 15:20 -- matched the time when
the issue occurred first that I couldn't write to the calendar anymore.

So, what did I do? -- Quit korganizer, then moved away those two files from
their current location (for backup, so I could have pushed them back if that
wouldn't have worked out), re-launched korganizer -- and voila, I could write
to the defaultly loaded calendar again.

I call this half a fix because you need to look yourself for whether it's lock
files which are in the way and then remove them manually.

But anyways, this looks like the cleanest solution so far for this issue.

I hope this was helpful for everyone who's still using KDE 3.5.x, like the
Debian (Lenny) world for example.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.