Version: 0.8.1 (using KDE KDE 3.5.1) Installed from: Debian testing/unstable Packages OS: Linux I dragged and dropped an image into a folder / album in konqueror expecting it to appear in the album in digicam which is does normally (about 90% of the time this works). Occasionally, like this time it didn't magically appear in the album view in digikam. Normally I would move the image to another folder (using konqueror) and drop it back into the album folder. Digikam always picks it up the second time (I presume this is a problem with notifications). Anyway, thinking that all this moving about was a pain I decided to import the image into the folder it was already in rather than move it out and back in again. Rather than simply importing the image a blank file was written and the image was lost! These instructions should probably reproduce the problem: 1)Drag and drop an image into a folder that is digicam thinks is an album until the image doesn't magically appear. 2)Right click on the album and select import > add images. 3)Import the image that is already actually in the folder on the disk. 4)A confusing replace the left image with the right image dialog pops up. The image on the right is the image on disk the left window mentions something about the image not existing. 5)Press ok. 4)The image on the disk is replaced with an empty file. This problem might also occur if you try and import an image that digikam already knows about into the album it's already in. I suspect that this might actually be a problem with KDE copy utility but I discovered it in digikam. Either way this is a problem that can easily result in data loss.
Graham, Is this problem still reproductible with last release of digiKam (0.9.2) and KDE3.5.x ? Gilles
Graham, What's news about this file ? Can you test using 0.9.4 release ? This still valid ? Thanks in advance Gilles Caulier
I no longer have a Linux box to test this on. I hope to have one in the near future and I will try this bug out then.
I would say that the issue is gone finally in 0.10 due to the changes Marcel did some days ago. All in all this bugreport is for 0.8.1, maybe we should just close it? If really needed, it can be re-opened again. Andi
as explained this bug should be fixed. Please reopen if you encounter the issue again in the future