Project

General

Profile

Bug #12726

unable to open image in running instance

Added by Paul Vasak 3 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
General
Target version:
-
Start date:
02/29/2020
Due date:
% Done:

0%

Estimated time:
Affected Version:
git stable branch
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I like to open images in darktable from within digikam or occasionally from the command line.
When darktable isn't running this works for the first image (albeit only if i temorarily move by dt-config directory and start with a completely fresh one, otherwise dt freezes before displaying the image - i suppose this is due to some inconsistencies in my config folder).
If I try to open another image while darktable is still running I get the following message on the command line and the attempt to open the image fails (started with darktable -d all):

[memory] at startup
[memory] max address space (vmpeak):      111832 kB
[memory] cur address space (vmsize):      111832 kB
[memory] max used memory   (vmhwm ):       22640 kB
[memory] cur used memory   (vmrss ):       22640 kB
[init] the database lock file contains a pid that seems to be alive in your system: 17188
[init] database is locked, probably another process is already using it
trying to open the images in the running instance
ERROR: can't acquire database lock, aborting.

Also available in: Atom PDF

Go to top