[KPhotoAlbum] KPA 3.1.0 RC1 not importing data / crash on cancel
lists at majo.name
Wed Oct 10 07:58:23 CEST 2007
> Ok, importing with the photos already present in the target directory
> now works "mostly".
> (All of the above mentioned problems are gone)
> There is one problem, which makes it quite useless:
> At startup KPA reads the new images. They are now present in the DB but
> with no tags.
> Reading the .kim files should now add the tags. But instead it leaves
> the original entries untouched and creates new entries.
> If the already present photo has a filename of 'x.jpg' the import
> creates 'x-2.jpg'. So in the end I have twice that much photos in the
> folder (as seen by KPA), one set with the real photo but no tags, a
> second set with a missing photo (grey with the edge snipped off) but the correct tags.
> Does the md5sum of duplicate match the original?
No, this is one example:
<image width="-1" startDate="2007-10-08T00:24:12" height="-1" endDate="2007-10-08T00:24:12" md5sum="b47ba441fdfc8926a1f181e138633ab7" file="test/IMG_0280.JPG" label="IMG_0280" angle="0" />
<image width="-1" startDate="2007-10-03T17:29:36" height="-1" endDate="2007-10-03T17:29:36" md5sum="00000000000000000000000000000000" file="test/IMG_0280-2.JPG" label="IMG_0280" angle="0" >
The copied photo has a checksum. The imported one has a list of zeros.
What works better, is to first import the .kim-file without the photos.
(Thanks for the button to avoid the asking for the photos)
Then copy the photos in place. The only downside is, that the md5 sum
doesn't get created:
<image width="128" startDate="2007-10-03T17:29:36" height="85"
file="test/IMG_0280.JPG" label="IMG_0280" angle="0" >
(This may be asking for too much: at the import the files aren't present
and on the next start the photos are already present in the DB)
Marking just those pictures and doing "Maintenance/Recalculate Checksum"
does the trick.
More information about the KPhotoAlbum