[digiKam-users] Crash when busy processing modified file system

[Maik Qualmann]

This crash is a bug in digiKam-6.3.0, which is fixed in digiKam-6.4.0.

https://bugs.kde.org/show_bug.cgi?id=411927

Maik

Am Montag, 4. November 2019, 21:11:02 CET schrieb Dougie Nisbet:
> One of the things I like about digiKam is how it deals with external
> changes to files. However, it seems that this is fragile. If I make a
> lot of external changes; e.g. filename renaming, I find DK copes fine.
> But only if I leave it alone for an hour or two. If I try to do pretty
> much anything while it's still busy scratching its head about the
> nonsense I've been up to while it was asleep, I get this sort of thing,
> and it Aborts.
> 
> It's not the end of the world. I can wait. But is there anything I can
> tweak? It usually involves lots of 'Datebase is locked' messages before
> it aborts.
> 
> This is digikam-6.3.0-x86-64.appimage on Debian.
> 
> Dougie
> 
> 
> 
> Digikam::ItemScanner::scanFromIdenticalFile: Recognized
> "/store/media/images/2004/01/18/Europe - Brussels -- Sun 18 Jan 2004
> 11-43-30 GMT.jpg" as identical to item 2213
> Digikam::ItemScanner::commit: Scanning took 3 ms
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
> locked. Waited 9500
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
> locked. Waited 9750
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
> locked. Waited 9750
> Digikam::ItemScanner::~ItemScanner: Finishing took 418 ms
> Digikam::DImg::load: "/store/media/images/2004/01/18/Europe - Brussels
> -- Sun 18 Jan 2004 11-43-35 GMT.jpg"  : JPEG file identified
> Digikam::ItemScanner::prepareAddImage: Adding new item
> "/store/media/images/2004/01/18/Europe - Brussels -- Sun 18 Jan 2004
> 11-43-35 GMT.jpg"
> Digikam::ItemScanner::scanFromIdenticalFile: Recognized
> "/store/media/images/2004/01/18/Europe - Brussels -- Sun 18 Jan 2004
> 11-43-35 GMT.jpg" as identical to item 2214
> Digikam::ItemScanner::commit: Scanning took 3 ms
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
> locked. Waited 10000
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Detected
> locked database file. There is an active transaction. Waited but giving
> up now.
> Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure
> executing query:
>   "SELECT id FROM Albums WHERE albumRoot=:a AND relativePath=:bb;"
> Error messages: "Unable to fetch row" "database table is locked: Albums"
> "6" 1
> Bound values:  (QVariant(int, 1), QVariant(QString, "/2014/07"))
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is
> locked. Waited 10000
> Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Detected
> locked database file. There is an active transaction. Waited but giving
> up now.
> Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure
> executing query:
>   "SELECT COUNT(id) FROM Images WHERE album=:a;"
> Error messages: "Unable to fetch row" "database table is locked: Images"
> "6" 1
> Bound values:  (QVariant(int, 2066))
> unknown: ASSERT: "!isEmpty()" in file ././/include/QtCore/qlist.h, line 345
> /tmp/.mount_digikaDHsM2n/AppRun: line 151: 30145 Aborted                
> digikam $@