Bug 229108 - digikam doesn't display all images after and upgrade
Summary: digikam doesn't display all images after and upgrade
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Schema (show other bugs)
Version: 1.1.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-02 11:02 UTC by markku.korkeala
Modified: 2017-07-26 05:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.2.0
Sentry Crash Report:


Attachments
Digikam messages when starting digikam (26.86 KB, application/octet-stream)
2010-03-02 11:18 UTC, markku.korkeala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description markku.korkeala 2010-03-02 11:02:36 UTC
Version:           1.1.0 (using KDE 4.4.0)
OS:                Linux
Installed from:    Fedora RPMs

Description of problem:

New version of digikam doesn't display images from most of my albums. This
years and last years albums work fine, but at least all photo albums before
2008 don't work. The photos are in the folders, I've tried to rescan my collection,
I've checked with SQLite the digikam4.db database file and it seams
the images belong to the album they supposed to be, but they just don't get
displayed for some reason.

Version-Release number of selected component (if applicable):
digikam-1.1.0-2.fc12.i686
Distribution is Fedora 12 (I've first filed bug report there,
https://bugzilla.redhat.com/show_bug.cgi?id=569011 )

How reproducible:
Happens everytime on my computer

Steps to Reproduce:
1. Open digikam
2. Open an album from 2007 containing images.

Actual results:
Nothing happens, doesn't diplay thumbnails, it displays on low left corner: No
item selected, it seems the album would be empty.

Expected results:
Thumbnails of albums images are displayed and at the bottom it displayes
selected image name; something like: imgp2323.jpg (1 of n)

Additional info:
Problem first started with digikam-1.1.0-1.fc12.i686, before that digikam worked fine.
Comment 1 caulier.gilles 2010-03-02 11:13:19 UTC
Run digiKam on a console and paste here all debug messages

Gilles Caulier
Comment 2 markku.korkeala 2010-03-02 11:18:28 UTC
Created attachment 41255 [details]
Digikam messages when starting digikam

Here are the messages.

Markku.
Comment 3 Marcel Wiesweg 2010-03-02 17:21:35 UTC
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?
Comment 4 markku.korkeala 2010-03-02 17:57:49 UTC
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.
Comment 5 Marcel Wiesweg 2010-03-10 18:58:46 UTC
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.
Comment 6 markku.korkeala 2010-03-12 18:29:56 UTC
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.
Comment 7 Marcel Wiesweg 2010-03-12 18:49:22 UTC
Workaround found. Finding the cause is difficult.