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
apparently i need to create a t(ruth)-table. The import file & import
folder behaves a bit differently. So I need to create a T-Table to see
watt r the conditions that will cause the failure.
i now just to need to document the conditions that will exact that
failure. :-/ just a bit different
So erasing contents os the xmp does me mo good in localizing the problem :-/
how does one FULLY erase db's memory recollection of that image? Delete
darktable image/data, then rename xmp file?
On 4/7/21 10:11 AM, Mica Semrick wrote:
Everything that is in the XMP is held in the db as well.
On
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
Everything that is in the XMP is held in the db as well.
On April 7, 2021 6:30:59 AM PDT, Postmaster 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
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
