It's a sqlite database. One way past this locking issue is to
clone it via dump, and then move the old file out of way. I keep
backups of my library like this:
--------
$ cat ~/bin/dtbackup.sh
#!/bin/bash
DTLIB=$HOME/.config/darktable/library.db
DTNEWLIB=${DTLIB}-`/usr/bin/date +%Y%m%d_%H%M`
ECHO=/bin/echo
SQLITE3=/usr/bin/sqlite3
RESULT=`$ECHO .dump | $SQLITE3 $DTLIB | $SQLITE3 $DTNEWLIB`
if [ $? -eq 0 ]; then
$ECHO "Dumped $DTLIB to $DTNEWLIB"
else
$ECHO "FAILED to dump $DTLIB to $DTNEWLIB"
exit $RESULT
fi
--------
On occasion I have needed that backup file, so I just copy it
to the correct filename and startup.
hth,
James
On 11/08/17 09:58 am, Patrick Shanahan wrote:
* David Vincent-Jones <david...@gmail.com> [08-10-17 19:54]:
A fresh install of the new Opensuse 42.3 and I get a new dt error when I
try to import files from my camera.
"darktable - error locking database
an error has occurred while trying to open the database from
/home/david/.config/darktable/data.db
the database lock file contains a pid that seems to be alive on your
system:7661"
The pid # changes if I close dt and retry
If I ignore the problem, continue and 'click on cameras' the error
message disappears and the import window opens.
I notice that the problem of selecting images to download still needs
the multi-tab workaround on this os version. That 'workaround' scenario
is not needed with the Tumbleweed Opensuse version
Am working with the up to date git.
maybe you didn't close darktable properly and left a lock file
stop darktable
ls -la .config/darktable |grep lock
rm -f .config/darktable/*.lock
try again
running Tw, don't know about a "multi-tab" work-a-round.
--
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
https://www.jmcpdotcom.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
