Summary: | digikam doesn't display all images after and upgrade | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | markku.korkeala |
Component: | Database-Schema | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, marcel.wiesweg |
Priority: | NOR | ||
Version: | 1.1.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.2.0 | |
Attachments: | Digikam messages when starting digikam |
Description
markku.korkeala
2010-03-02 11:02:36 UTC
Run digiKam on a console and paste here all debug messages Gilles Caulier Created attachment 41255 [details]
Digikam messages when starting digikam
Here are the messages.
Markku.
Did you use a recent digikam version to upgrade from a 0.9 digikam database? Then this would be bug 226853. If not, can you send me the digikam4.db file? I've used the fedora digikam packages and used the 0.10.x series, and 1.0.0 before the 1.1.0 and didn't have problems. The bugreport sounds kind of same, but some album displays images and some don't. But I played around with digikam4.db file, and using this sql statement: select * from images im, imageinformation ii where im.album = 455 and im.id = ii.imageid; (and changed the im.album to see output for different albums ), and it seems that most of my images are missing row in the imageinformation table, only those images that are displayed by digikam returns also rows from above select statement. This is the reason I digikam don't display most of my images? Can I somehow send a subset of the digikam4.db file, I rather not send the whole file to strangers, due privacy concers, unless really necessary. I can run any test you need with file. A missing line in ImageInformation is indeed known to cause problems like this, #226853 was essentially the same problem. The statement INSERT INTO ImageInformation (imageId) SELECT id FROM Images; should fix this problem. Afterwards you can go to the affected album and from the menu "Reread metadata from images". I suspect a problem similar to 226853, but I am not sure about the real cause. Thanks for suggestions, I tried statement: "REPLACE INTO ImageInformation (imageId) SELECT id FROM Images;" from bug #226853 and it worked. For the cause I'm not sure either. Workaround found. Finding the cause is difficult. |