darktable icon indicating copy to clipboard operation
darktable copied to clipboard

After opening an ARW file and returning to lighttable, that image is gone from the library and cannot be readded without renaming

Open DT-one opened this issue 9 months ago • 6 comments

Is there an existing issue for this?

  • [x] I checked and did not find my issue in the already reported ones

Describe the bug

Similar to this issue: https://github.com/darktable-org/darktable/issues/14446

Working with RAW images from a Sony alpha7s

Images are loaded into the library and can be opened for editing. When returning to the lighttable to copy the history stack, the image is gone. Upon trying with another image, upon returning to the lighttable, it is gone to. When trying to re-add the image to the collection through drag and drop from file explorer, it does not appear in the lighttable. If all images are removed from the lighttable, the .xmp files deleted, and the whole collection is dragged back in, all images appear except those that had been opened earlier. If the file is renamed and dragged back in appears on the lighttable. Again, upon editing it, it disappears from the light table.

No errors are thrown throughout all of this.

Its like the image goes on some sort of black list.

Steps to reproduce

See above

Expected behavior

The images should remain in the lighttable. If they are gone, they should be able to be re-added

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.0.1

What OS are you using?

Windows

What is the version of your OS?

Windows 10

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

DT-one avatar Mar 07 '25 06:03 DT-one

  • Ando @.***> [03-07-25 01:59]:

DT-one created an issue (darktable-org/darktable#18515)

Is there an existing issue for this?

  • [x] I checked and did not find my issue in the already reported ones

Describe the bug

Similar to this issue: https://github.com/darktable-org/darktable/issues/14446

Working with RAW images from a Sony alpha7s

Images are loaded into the library and can be opened for editing. When returning to the lighttable to copy the history stack, the image is gone. Upon trying with another image, upon returning to the lighttable, it is gone to. When trying to re-add the image to the collection through drag and drop from file explorer, it does not appear in the lighttable. If all images are removed from the lighttable, the .xmp files deleted, and the whole collection is dragged back in, all images appear except those that had been opened earlier. If the file is renamed and dragged back in appears on the lighttable. Again, upon editing it, it disappears from the light table.

No errors are thrown throughout all of this.

Its like the image goes on some sort of black list.

what filters do you have set?

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

ptilopteri avatar Mar 07 '25 15:03 ptilopteri

Try clicking on the reset icon on the "collection filters" module in the left sidebar, even if you haven't set any filters. There's an unintialized-value bug which sometimes causes images to be filtered out at startup even when no filters are set. This is most easily seen when importing a folder of images from the commandline.

ralfbrown avatar Mar 07 '25 16:03 ralfbrown

Ah yep

Toggling from 'all images' to 'custom' (chosen at random) and back again also seems to fix the behaviour.

Upon removing the images from the library and re-adding the same images the bug behaviour does not return.

Upon closing dark table and adding another folder of images the issue does not return.

Thankyou for proposing the work around!

Image

DT-one avatar Mar 08 '25 04:03 DT-one

Yes, that's the uninitialized-value bug I mentioned. What you did forces its initialization just like clicking the reset icon.

ralfbrown avatar Mar 08 '25 18:03 ralfbrown

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar May 08 '25 00:05 github-actions[bot]

Assuming this bug got patched?

DT-one avatar Jun 09 '25 01:06 DT-one

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

github-actions[bot] avatar Aug 09 '25 00:08 github-actions[bot]