Bug 107004

Summary:	Calendar data is lost when stale file handle is reactivated
Product:	[Applications] korganizer	Reporter:	Kde <kde>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	3.4
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Kde 2005-06-08 02:07:32 UTC

Version:           3.4 (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-20a-default

On my laptop I use an IPsec tunnel via wlan to connect to my server which holds a KOrganizer calendar on an NFS share. This calendar is marked as read-only in the KDE control panel. There is a local (empty) calendar, which is deactivated however (for some reason it was deactivated, even though it was the standard ressource; this also seems to be a bug).
I usually use suspend-to-disc when shutting down the laptop, even after the NFS filesystem was mounted (via IPsec). Before suspending, I log out of KDE.

Now, when I bring the system back up, I log in to KDE and use kwlanassistant to reconnect to the wireless network. Until then, the NFS directory just hangs (mount option 'soft' is set). As soon as the connection is back up and the tunnel is running, NFS comes back and the KOrganizer notifier pops back up in kicker.
This is the point when KOrganizer completely wipes out all my calendar data!

Comment 1 Kde 2005-06-08 02:14:16 UTC

http://bugs.kde.org/show_bug.cgi?id=107005 is the other (possibly related) bug.

Comment 2 Reinhold Kainhofer 2006-11-02 19:07:55 UTC

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

Comment 3 Denis Kurz 2016-09-24 18:48:54 UTC

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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:27:39 UTC

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.