Hi, there is a workaround:
darktable ships an utility called "purge_non_existing_images.sh". If you move the problematic picture to a different location and run the script with "purge_non_existing_images.sh --purge", it will remove the data for this image from the database because the path stored in the database does not exist anymore. kind regards, Simon Am 07.04.21 um 16:35 schrieb Postmaster: > Since i cant get darktable to run without crashing, i cant erase the > picture from its memory. > do I have to delete the .db file before i run darktable? > > On 4/7/21 10:11 AM, Mica Semrick wrote: >> Everything that is in the XMP is held in the db as well. >> >> On April 7, 2021 6:30:59 AM PDT, Postmaster <postmas...@gatworks.com> >> wrote: >>> Which leads me to think that the history of the picture is being kept >>> in >>> an alternate place. Like somewhere in .cache. Maybe a .db? >>> OR is it my imagination that something more is happening to me. >>> ___________________________________________________________________________ >>> >>> darktable developer mailing list >>> to unsubscribe send a mail to >>> darktable-dev+unsubscr...@lists.darktable.org >> >> ___________________________________________________________________________ >> >> darktable developer mailing list >> to unsubscribe send a mail to >> darktable-dev+unsubscr...@lists.darktable.org >> >> > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
