Bug 342313

Summary: SQLITE : detected locked database file. There is an active transaction. Waited but giving up now.
Product: [Applications] digikam Reporter: Thomas Arend <thomas>
Component: Database-SqliteAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: critical CC: caulier.gilles, jwrigley7, thomas
Priority: NOR    
Version: 4.5.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 4.12.0

Description Thomas Arend 2014-12-29 17:07:45 UTC 
Digikam does not start and reports 

Dgikam::DatabaseCoreBackendPrivate::checkRetrySQLiteLockError:
Detected locked database file. There is an active transaction. Waited but giving up now.
Comment 1 James W 2014-12-30 07:43:32 UTC 
Hi there,
Have you seen this? http://mail.kde.org/pipermail/digikam-users/2012-July/016627.html

(note: I'm a Google Code-in student)
Comment 2 Thomas Arend 2014-12-30 15:19:23 UTC 
No!

But after l long, long time digikam stoped waiting. Now it runs.

There should be a hint in the status bar when digikam has such problems.

Thomas
Comment 3 caulier.gilles 2015-05-10 17:04:15 UTC 
Maik, 

I suspect that DB lock is now fixed with your patch in Import tool and BQM. Right ?

Gilles
Comment 4 caulier.gilles 2015-06-25 13:02:51 UTC 
Git commit 901788011ff6489a63ccdbb5ade0b6438f74f0e8 by Maik Qualmann.
Committed on 28/04/2015 at 19:05.
Pushed by mqualmann into branch 'master'.

apply patch #92305 to suspend collection scan when the BQM is running
FIXED-IN: 4.10.0

M  +2    -1    NEWS
M  +2    -0    utilities/queuemanager/main/queuemgrwindow.cpp

http://commits.kde.org/digikam/901788011ff6489a63ccdbb5ade0b6438f74f0e8