* Dave <[email protected]> [03-06-14 12:54]: > On 6 Mar 2014 19:33, "Dave" <[email protected]> wrote: > Sigh. > I'm making noise again. > To answer my own question: There is a file called > .config/darktable/library.db.lock which I renamed. > Problem solved. > > Relax everyone I got this! :D > > Hello. > > I'm using darktable from git. > > Today I get a "database locked perhaps another process is using it" > > message. > > Can anyone offer a solution?
Remove it rather than renaming it. It is to keep addiitonal database access from making uncoordinated changes, ie: duplicate access to the same records. When darktable fails or faults out, the db file lock is not removed. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
