Orphan xmp files in very recent darktable

Last night I looked inside my image files for the first time in a while… and found stacks of orphan xmp’s. That meaning the sidecar files of image files I had deleted.

I don’t know which of the last two dt installations is responsible (3.1.0+426 or +546??), I’ll need to do some testing tonight before raising this on github. But has anyone else seen this? I’m running Windows 10 pro, in case it should turn out to be a security “feature” (but it allowed the dng’s to be deleted, so I doubt it).

Yep, when you remove a photo in dt, it’s the entry in the dt database that’s removed, not the xmp file…

This is new… until now, if you used “selected files → trash”, both dng & xmp went to the trash. Now only the dng goes, which makes keeping the xmp fairly useless.

The “trash” button gets rid of the xmp file also (at least in DT 3.0.0, which is the version I have installed).

I did notice it before 3.0 with cloned photos…

Before & including 3.1.0+git256 it worked perfectly.

Le jeu. 6 févr. 2020 à 12:36, manu’ via discuss.pixls.us noreply@discuss.pixls.us a écrit :