[Digikam-devel] [Bug 246743] New: digiKam ate my image (file truncated to 0 byte after tagging)

[Marc Aurel]

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

           Summary: digiKam ate my image (file truncated to 0 byte after
                    tagging)
           Product: digikam
           Version: 1.3.0
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Tags
        AssignedTo: digikam-devel at kde.org
        ReportedBy: marc-keyword-kdebug.e348b5 at a42.de


Version:           1.3.0 (using KDE 4.4.95) 
OS:                Linux

Howdy, I'm a new user, trying to regain my freedom by evaluating digiKam as a
replacement for Picasa. ;)

I'm working on a Ubuntu 10.04 system with Digikam 1.3 and KDE
4:4.4.92-0ubuntu1~lucid1~ppa1 from the kubuntu PPA, my image folders are
located on a NFS server and were added to Digikam as local folders.


Reproducible: Didn't try

Steps to Reproduce:
I think this is what I did:
- I selected many raw images in a folder (CRW files)
- I tagged them with one keyword
- While the pictures were tagged, which took a while (!), I selected a
different subset of images
- I tagged that new selection with another keyword and/or added a caption (I'm
not sure anymore) while the first tagging process still was working, I noticed
the thumbnails being refreshed

(I don't expect my result to be easily reproducible, though... looks like a
race condition....)


Actual Results:  
One of the thumbnails turned into a "broken" image. Upon inspection, the
underlying file proved to be 0 byte in size. The corrupted image was supposed
to be tagged with both keywords, I think.



Expected Results:  
In the digiKam settings, section Metadata, the option "Write Metadata to RAW
files (experimental)" was NOT enabled. Perhaps I'm misunderstanding
something... why does digiKam touch raw CRW files during tagging when this
option is disabled? 

So the expected result would have been an unchanged and uncorrupted image and
instantaneous tagging only in the digiKam database.


There was no other imaging application running that could've accessed the
folder simultaneously. And my systems don't have a history of spontaneous file
combustions.

This could very well be considered a major bug, as it corrupted the user's
data. ;)

Luckily, this didn't happen immediately after an import, so I had a backup of
the image. It was a scary experience anyway, though.

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