Bug 52851

Summary:	bad handling of disk full conditions
Product:	[Applications] korganizer	Reporter:	Alistair Mann <kdebugs>
Component:	general	Assignee:	Cornelius Schumacher <schumacher>
Status:	RESOLVED FIXED
Severity:	normal	CC:	schampailler, schumacher
Priority:	NOR
Version:	3.0.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alistair Mann 2003-01-10 15:36:39 UTC

Version:           3.0.1 (using KDE 3.0.3)
Installed from:    compiled sources
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:          Linux (i686) release 2.4.18

At a disk full condition, korganizer if asked will try to save out its .ics file, but will actually only manage to truncate the disk copy to 0 bytes long. A disk full condition may therefore cause the loss of open .ics files.

Korganizer may be expected to conduct a save by first saving to a temp filename, and on successful completion moving the temp to the original. At worst, losses will be confined to that entered since last update.

Cheers,
-- 
Alistair Mann

Comment 1 Reinhold Kainhofer 2003-09-19 12:39:05 UTC

*** Bug 62996 has been marked as a duplicate of this bug. ***

Comment 2 David Faure 2003-11-24 10:53:22 UTC

Subject: Re: [Kde-pim] Patch: using KSaveFile in libkcal

On Monday 24 November 2003 10:19, Reinhold Kainhofer wrote:
> Am Montag, 24. November 2003 08:49 schrieb David Faure:
> > After ending up with a corrupted karm.ics once more, due to a full
> > partition, I decided it might be time for libkcal to use KSaveFile.
> >
> > See attached patch.
> 
> Great. Does this finally fix bug:52851?

Indeed.

Comment 3 Christian Mercat 2004-09-29 14:08:05 UTC

I don't see that this bug 52851 is fixed, I am using 3.1.1 and audacity just swamped my disk, causing the loss of my calendar, it's a tragic loss for me. I suggest as well an automatic backup in order to be able to retrive my yesterday's calendar.

Comment 4 Reinhold Kainhofer 2004-09-29 14:16:22 UTC

It is fixed. It's just that the fix didn't go into kde 3.1.1, but it's probably in 3.2 (in 3.3 for sure).

Cheers, Reinhold