Yep. That worked. Thanks. To summarize:
$sudo reboot $cd ~/.config/darktable $mv library.db library.db.orginal start darktable as normal close darktable $cp library.db,original library.db start darktable as normally done everything was as it was before the dirty shutdown. There're probably more elegant ways of clearing the lock, but this approach worked for me. On 2013-04-02 16:50, Patrick Shanahan wrote: > * Mark Heieis <[email protected]> [04-02-13 19:42]: >> I deleted the file ~/.config/darktable/library.db and now it starts >> again. I didn't have much in the db so I don't think I lost much info. I >> did save the db so I can recover it, if I find out how to "unlock" it. >> > Shut down darktable *normally* and replace current library.db with your > saved version. ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
