Bug 180351

I confirm this bug.

I just copied this file in my collection when digiKam running.

The file appear in icon view, but all photograph information are not imported to the database automatically.

Created attachment 30138 [details]
file imported to digikam (1)

Created attachment 30139 [details]
file imported to digikam (2)

Marcel,

re-starting digiKam do not help.

Going to Caption & Tags and using More/Read Metadata from File to Database do not help

Gilles Caulier

Marcel,

I found a way to see photograph information with this image.

1/ stop digiKam
2/ copy file to collection
3/ start digiKam
4/ if scan for new image at startup is not set on, start it manually from Tools menu
5/ The image is now on icon view with all photograph info.

Gilles Caulier

Created attachment 30180 [details]
file imported to digikam (3)

Screenshot of file imported in digiKAm with all photo info available.

Sebastian, 

Can you confirm my investigations from #5 ?

Gilles Caulier

No problem for me here, everything from the metadata is shown. No difference if imported with digikam running or not (of course, I removed the database entries before). Can you reliably reproduce this?

Marcel,

Are you changed something in code ?

Why it doesn't work here ? It's relevant of digikam4.db file ? I need to remove it before to test again ?

Gilles

No I'm not aware of any relevant changes - it just works here...
(I updated exiv2 yesterday because of the other bug, that's the only change I see here)

To re-import from scratch, remove the whole digikam4.db, or just remove all entries for this file:
DELETE FROM Images WHERE name ='pict2826.jpg';
(Hope you have no other image with the same name;-) )
and restart digikam, or remove the file and add it while digikam is running.

If you can reproduce, it would be interesting to get a database dump:
SELECT * FROM Images LEFT JOIN ImageMetadata ON imageid=id WHERE name ='pict2826.jpg';

Marcel, trying to import again this image in my collection when digiKam already running doesn't work. No photo info avaialble.

Are you see that Color Mode of this image is YCbCr not RGB. Perhaps it's the problem? 

See below the database dump:


[gilles@localhost photo]$ sqlite3 digikam4.db
SQLite version 3.6.1
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> SELECT * FROM Images LEFT JOIN ImageMetadata ON imageid=id WHERE name ='pict2826.jpg';
1269|120|pict2826.jpg|1|1|2009-01-11T20:36:52|3621253|79196ae66df7c4fec30ebca48983a026|||||||||||||||||
1271|147|pict2826.jpg|1|1|2009-01-17T09:36:57|3621253|79196ae66df7c4fec30ebca48983a026|||||||||||||||||
sqlite>

Gilles

Marcel,

Renaming digikam4.db to digikam4.db.old solve the problem.

Runing digiKam and importing the file again in collection work fine now.

I will attach bziped DB file for investiguations...

Gilles

Created attachment 30339 [details]
old digikam4.db database file archived

Created attachment 30340 [details]
new digikam4.db database file

Sebastian, 

Please rename your digiKam database file as explained before in this thread and try again.

Gilles Caulier 

I cannot find out why this image was imported without metadata information into the database at first, if new attempts with a fresh database do not reproduce this.
I see some related TODOs. The collection scanner perhaps relies a bit too strongly on information it has already in its database. We also need to clear up the actions "Refresh", "Synchronize Images with database", "Update Metadata database", "More->Read metadat from file to database", "More->Write metadata to each file", sometimes do not do what they say (or they are unprecise in saying what they do), or it is not really clear which images are affected. But I would prefer to do that when the batch manager is implemented.

Marcel,

Do you think that we can close this file now ?

Gilles

Let's close this file now. No more actions to be expected.