Bug 145034

Summary: korganizer: breaks hard links
Product: [Frameworks and Libraries] Akonadi Reporter: Olivier Vitrat <ovit.debian>
Component: ICal file resourceAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: smartins
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:

Description Olivier Vitrat 2007-05-04 17:02:08 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Debian stable Packages

Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=337225

When you close kontact and it has accessed read-write, even if not
written in it, a file that has more than one hard link, kontact creates
a new file at the path it has accessed, with a new inode, thus
"breaking" the hard links (their content wil not be updated anymore).

Here's my steps to reproduce the bug:

$ cat > foo.ics <<EOF
BEGIN:VCARD
CLASS:PUBLIC
FN:John Smith
N:Smith;John;;Mr;
TEL;TYPE=CELL:+123456789
VERSION:3.0
END:VCARD
EOF
$ stat -c "%i %n" *
1917526 foo.ics
$ ln foo.ics bar.ics
$ stat -c "%i %n" *
1917526 bar.ics
1917526 foo.ics
$ kontact

Add foo.ics as a new address book, read-only, quit kontact.

$ stat -c "%i %n" *
1917526 bar.ics
1917526 foo.ics
$ kontact

Remove foo.ics address book. Quit kontact.

$ stat -c "%i %n" *
1917526 bar.ics
1917526 foo.ics
$ kontact

Add foo.ics as a new address book, read-write, quit kontact.

$ stat -c "%i %n" *
1917526 bar.ics
1918815 foo.ics
1918812 foo.ics_4

OK, link's broken...

I had the same bug with my calendar, thus the bug filed on kontact. I
suspect it is a general KDE bug.
Comment 1 Denis Kurz 2016-09-24 20:38:13 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:09:07 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.