Project

General

Profile

Bug #10011

sqlite complains with "cannot start a transaction within a transaction"

Added by Torsten Bronger over 5 years ago. Updated over 4 years ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
General
Target version:
-
Start date:
07/11/2014
Due date:
% Done:

10%

Estimated time:
Affected Version:
git development version
System:
Ubuntu
bitness:
64-bit
hardware architecture:
amd64/x86

Description

While DT's startup, there are the attached sqlite3 error messages in the console. Basically, at some places the following two errors are triggered:

sqlite3 error: /tmp/darktable/src/iop/atrous.c:767, function init_presets(): cannot start a transaction within a transaction
sqlite3 error: /tmp/darktable/src/iop/atrous.c:942, function init_presets(): database is locked

This is not introduced by a recent change. In fact, at least since March 2014 this problem exists. I could not test older revisions because of DB incompatibilities. Romoving the DB and re-importing everything solves the issue.

output.txt (2.71 KB) output.txt Console output Torsten Bronger, 07/11/2014 08:54 AM

History

#2 Updated by Roman Lebedev over 5 years ago

I also encountered "sqlite3 error: /home/lebedevri/darktable/src/iop/exposure.c:207, function init_presets(): cannot start a transaction within a transaction"
For me it happened after 3e2d49b (as a date reference, first and only time i saw that message, not bad commit)

#3 Updated by Torsten Bronger almost 5 years ago

  • % Done changed from 0 to 10
  • Status changed from New to Confirmed

I hit the problem again. Currently, I use DT 1.7.0+1130~g9419cbc.

The affected library.db can be downloaded from http://wilson.bronger.org/library.db.bz2.

I consider this a quite serious problem: The database cannot be updated anymore, any changes only land in the XMP files, and there is no notification of this problem besides the fact that DT requests at every startup to re-import XMP files that are newer than the database. And even this only happens if you activated the check for it.

#4 Updated by Torsten Bronger over 4 years ago

Usually, my library.db is on an NFS mount. This issue may be NFS-related, as a reboot without the NFS mount, but with the same images and library.db file, solved the problem on my computer.

Also available in: Atom PDF

Go to top