I downloaded a RAW image, which was successfully imported in the DB. I converted it, and started working on it : 2 versions made, one in BW and crop, the other in colours. Both in JPG. Versioning correct as long as was in the editor. When I close the editor, the images does not show in the thumbnails. They are present in the root folder of my DB. If I try to add them a second time in the DB by dragging them from a file manager, it says they are already there. If I make a copy, nothing happens after this message. If I choose to move them, they are simply deleted from my DB root folder. No workaround found for now. Reproducible: Sometimes DigiKam 2.5.0 Linux (x86_64) release 3.2.0-24-generic gcc
Problem have been already reported and fixes have been introduced with last 2.6.0 Release Candidate. Can you try with this version if problem occurs again ? Gilles Caulier
If you pressed "Save changes" and did not explicitly enable the option to show originals, you probably see the desired behavior. If you pressed "Save as new version" both times it's a bug.
2.5.0 is the version available with Kubuntu. The way to reproduce it : Add a RAW in your DB Import it, and change the levels Save. Image disapeared... If you : Add a RAW in your DB Import it Save Change the levels Save It works.
Is there a way to make the images reappear in the DB ? I need them...
Maybe an artefact of versioning. Try to enable versioning (non-destructive editing and versioning is the name) in the options so that all fine-grained options are editable. Afterwards enable the two bottom-most checkboxes so that all images will be shown. Apply and disable versioning afterwards again. Does this help?
Official digiKam 2.6.0 release is out since few days now : http://www.digikam.org/drupal/node/656 Please, check if this entry still valid, or update report accordingly. Thanks in advance. Gilles Caulier
ag.perron, What's new about this file using last digiKam 3.5.0 ? Gilles Caulier
ag.perron, We need a fresh feedback here using last digiKam 4.2.0... Gilles Caulier
I didn't have any new occurences of this bug since 3.5.0, I did not update to 4.2.0 (not available automatically with kubuntu). I should perhaps try tu manually update !