[Digikam-devel] [digikam] [Bug 338842] New: Moving DNG images to another album corrupts DNG properties
Sander van der Heijden
smvdheijden at gmail.com
Sat Sep 6 12:29:36 BST 2014
https://bugs.kde.org/show_bug.cgi?id=338842
Bug ID: 338842
Summary: Moving DNG images to another album corrupts DNG
properties
Product: digikam
Version: 4.2.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Albums GUI
Assignee: digikam-devel at kde.org
Reporter: smvdheijden at gmail.com
When moving a large number of DNG images to another collection, some of the DNG
images have incorrect data. If this happened the DNG images are no longer
displayed when filtering on DNG images.
I've noticed the images table in the sqlite database contains 2 records for
each of the moved images, for the corrupted images the first record contains a
strange modification date and file size:
3673 {null} DSRC-6648.dng 3 1 1970-01-01T01:00:00 0
3880 25 DSRC-6648.dng 1 1 2014-09-06T12:37:25 21463202
e2617c5e0b6e1c6bc07634960f578831
Reproducible: Sometimes
Steps to Reproduce:
1. Convert a large number of RAW images (>100?) in a specific album to DNG
2. Move the converted DNG images to a different album
3.
Actual Results:
Most of the DNG images are moved correctly, but for some images some off the
image data is lost:
- Tooltip in grid layout shows some properties (amongst which size) to be
unknown
- DNG files are not displayed in grid while filtering DNG images
- Images table in sqlite db contains 2 records for each image, with one
record's modification date 1970-01-01 and filesize 0
Expected Results:
- Image properties (like size) should be preserved
- DNG files should be visible while filtering DNG images
- Images table in database should contain a single record with updated album id
If an image is corrupted, the only way, as far as I know, to fix the image, is
to delete all the records in the database with the specific image name...
Running Digikam 4.2.0 in Kubuntu 14.04
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list