Version: digiKam: 0.9.4 (using KDE 4.1.2) OS: Linux Installed from: Unspecified Linux Digikam told me to submit this Bug! This is what it told me: sqlite_step error: database disk image is malformed on query: SELECT Albums.url||'/'||Images.name FROM Images, Albums LEFT JOIN ImageProperties on Images.id = ImageProperties.imageid WHERE ( ( (Images.dirid IN (SELECT id FROM Albums WHERE url LIKE '%winter%')) OR (Images.name LIKE '%winter%') OR (Images.id IN (SELECT ImageTags.imageid FROM ImageTags JOIN TagsTree on ImageTags.tagid = TagsTree.id WHERE TagsTree.pid = (SELECT id FROM Tags WHERE name LIKE '%winter%') OR ImageTags.tagid = (SELECT id FROM Tags WHERE name LIKE '%winter%') )) OR (Images.dirid IN (SELECT id FROM Albums WHERE caption LIKE '%winter%')) OR (Images.dirid IN (SELECT id FROM Albums WHERE collection LIKE '%winter%')) OR (Images.caption LIKE '%winter%') OR (ImageProperties.value LIKE '%winter%' and ImageProperties.property='Rating') ) ) AND (Albums.id=Images.dirid) LIMIT 500; By the way I have Mysql
Can you give us a GDB backtrace ? Gilles Caulier
I'll try to reproduce ... but as long as i remember there was only this error dialog .... How do I produce a gdb backtrace?
Look here : http://www.digikam.org/drupal/contrib Gilles Caulier
Created attachment 30551 [details] Screenshot taken from start of DigiKam
(sorry too lazy to compile loaded debug symbols from ubuntu pakets) Ok something went really wrong here.. DigiKam claims out that there are images missing. But they still exist only the path is wrong. Look at the attachment.
at almost any picture this error is shown: Warning: JPEG format error, rc = 5 and there are two things I have to mention: * I have 64bit System * The images are on a samba drive (Debian) (yes i know i shouldn't but that's my primary image drive)
Claus, What's news about this entry. It still valid ? Can you try to use digiKam 0.10.0 for KDE4 ? Gilles Caulier
Marking as NEEDSINFO
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
With 5.0.0, the crash is not reproducible anymore. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier