[Digikam-users] [Feature Request] Catch crashes in third party subsystems and handle them inside digikam

Gilles Caulier caulier.gilles at gmail.com
Sat May 24 05:16:41 BST 2014

About Sqlite, A upstream patches have been applied in top level, but
not yet applied to all distribution. See the long story in this bug
report :


About Exiv2, library must be patched. It's not yet done.

Gilles Caulier

2014-05-24 4:49 GMT+02:00 James R. Shipman <JimShip at sbcglobal.net>:
> Digikam as currently designed is vulnerable to crashes in third party
> subsystems.  This has showed up strongly with the current problems with
> sqlite and exiv2 where digikam simply dies every time one of its subsystem
> crashes.
> I would suggest that a better way would be to catch these crash events and
> either handle them (for example skip a file that caused exiv2 to crash) or
> at least to die gracefully.
> Not doing this causes digikam to suffer in its reputation and in the worst
> case to make it unusable.  Right now when I start digikam and just let it be
> idle, then a few minutes later it simply disappears. Crashing while scanning
> metadata in the background.  I have been trying to filter out the offending
> files (*.MTS files in my case), but I have to be fast because while I'm
> trying to change digikam settings (filter out mts type) it will still crash
> causing me to have to start all over.  This is really bad behavior.
> Jim Shipman
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users

More information about the Digikam-users mailing list