Summary: | kphotoalbum crashes while scanning for new images | ||
---|---|---|---|
Product: | [Applications] kphotoalbum | Reporter: | Knut Esztermann <knut> |
Component: | general | Assignee: | KPhotoAlbum Bugs <kpabugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | blackie, denis.heidtmann+bugs, miika.turkia |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | image file from an S20 HP scanner under Win 2k (VirtualBox) |
Description
Knut Esztermann
2010-05-16 23:52:38 UTC
First impression from the backtrace indicates the problem to be in libexiv2 library. If that is the case then the exiv2 library needs fixing. In any case the problematic files would be useful to verify the problem. Yes, please email me at blackie@kde.org with the bogus files. I agree with thebro that it likely is a bug in the file or in exiv2, but it would be nice to confirm I am running the same version of KPA, KDE 4.4.2 in Ubuntu 10.04 LTS. I get a seg fault if I click on the "Recreate Exif search database". I had a similar crash after adding files, so I removed the new files and used my backups to replace exif-info.db and index.xml. Now I can use KPA, but "Recreate Exif search database" produces a reliable, reproducible crash. I note that executing "Recreate Exif search database" is what is required when adding new files. I tried to get the debug libraries for KPA without success. Where are they? -Denis Doing more exploration--Ran the demo, quit KPA saving the demo files in /tmp. Examined exif-info.db in /tmp/kphotoalbum-demo-parents. It is SQLite 3. The exif-info.db file in my photo collection is SQLite 2. Could this be why "Recreate Exif search database" causes a seg fault? Is there a way to fix this? -Denis Try deleting (make a backup) the exif-info.db. Deleted exif-info.db. Started KPA. A new exif-info.db was created--3KB, SQLite3. KPA crashes as before when trying to Recreate Exif search database. -Denis I added a .jpg file to the saved demo files. The demo ran fine; Recreate Exif search database worked as it should. -Denis The recreate db works for me just fine. What is your version of libexiv2? Upgrading that might be the solution. If that does not do it, the problematic file(s) should be identified and used to debug the problem. We cannot do much without means to reproduce the crash... My version of libexiv2 is 0.19. Synaptic says that is the latest. Are you saying that one or more of my image data files may be the cause of the problem? -Denis On Mon, Sep 13, 2010 at 10:19 AM, <miika.turkia@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=237889 > > > > > > --- Comment #8 from <miika turkia gmail com> 2010-09-13 19:19:33 --- > The recreate db works for me just fine. What is your version of libexiv2? > Upgrading that might be the solution. If that does not do it, the > problematic > file(s) should be identified and used to debug the problem. We cannot do > much > without means to reproduce the crash... > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > Created attachment 51869 [details]
image file from an S20 HP scanner under Win 2k (VirtualBox)
One of many files which cause a crash. Stripping exif data eliminates the problem.
I have found that I have 11 proven .jpg files which cause a crash, and perhaps 88 more. If I strip the exif data using jhead -purejpg <file>, the resulting .jpg does not cause a crash. The test is to copy the suspect file into the /tmp folder for the demo, then rescan for new images. The files were generated using an HP scanner running under Windows (VirtualBox). I am running: kphotoalbum 4.1.1-2ubuntu1 (Synaptic shows this as the Latest Version.) libexiv2-6 0.19-1 (also shown as Latest Version) Ubuntu 10.04 LTS A faulty file is attached. This should be fixed now in revision 1208526. |