Version: 0.9.0 (using KDE KDE 3.5.5) Installed from: SuSE RPMs Remove some files or directories below the image directory while digikam is not running. Start digikam, option "Scan for new items at startup" is turned off. This might not be necessary though. When selecting "Scan for new images", I get the message about items found in the database but not on the filesystem. When I select, that I do not want to remove them from the database, digikam just ends silently without leaving a backtrace in the crash handler.
I can reproduce with digikam from trunk (0.9.1 r624276). Digikam doesn't crash, but simply exits (see backtrace below), which is not expected behaviour. $ gdb digikam ... digikam: ImagePlugin_Charcoal plugin loaded digikam: ImagePluginLoader: Loaded plugin ImagePlugin_Charcoal kio_digikamtags: *** kio_digikamtag started *** digikam: ScanLib: Finding non-existing Albums: 31 ms digikam: ScanLib: Finding items not in the database or disk: 67 ms digikam: ScanLib: Updating items without date: 0 ms Program exited normally. (gdb)
This is what is expected behaviour - the dialog clearly tells the user the following: "digiKam cannot continue without removing the items from the database because all views depend on the information in the database. Do you want them to be removed from the database?" So if you select No, digikam cannot continue and therefore will exit. If you click No, it is expected that you will try to resolve the missing files problem before starting digikam. If these photos are actually removed, you should select Yes instead.