I observed a bug with darktable 2.6.2 on Arch Linux when updated sidecar files are found on startup and are reloaded: The updates are not completely picked up by reloading.
To reproduce: set up two user spaces with options "look for updated sidecar files on startup" and "write sidecar file for each image" enabled. - User A: - Open darktable. - Setup a collection of one image. - Mark it with a color label. - Close darktable. - User B: - Open darktable. - Import the same collection with this one image possibly reloading the sidecar files. - Close darktable. - User A: - Open darktable. - Delete the color label from the image. - Close darktable. - User B: - Open darktable. - Reload the sidecar file on startup. Now the database of User B is out of sync with the sidecar file. The image will have the color label still set in the database user B. Sometimes I observed that the side car files for a group of a raw and a jpg image get out of sync and only the sidecar file for the raw image does not pick up all the changes by the other user. I don't have a way to reproduce this behavior. J. Schray -- Jörg Schray Berlin ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
