https://bugs.kde.org/show_bug.cgi?id=433822
--- Comment #8 from [email protected] --- > I am happy to carry on troubleshooting Yes, my test file had had the metadata written back into them, that and the advanced settings meant that reading extended attributes would have been "at the bottom of the list" Testing, step by step (using the "old build" of 2021-03-02) Configured digiKam metadata settings, leaving 'Advanced' setting as default, close digiKam Created clean test files (confirming no embedded metadata), set Tags and Ratings values in xattr for some of the test files Ran digiKam, confirm that it picked up the images. ... It had not picked up the xattr values ... but that can be explained by the default 'Advanced' settings Reconfigured digiKam settings, clearing the selections to read/write embedded metadata under 'Advanced' for tags and ratings Changed xattr Tags/Ratings (via Dolphin), reran digiKam. ... Changes were not seen. Ohh... :-( Updated timestamps on all test files, with "touch *" ... ... Changes became visible after an F5 refresh. Ahhh :-) Changed tags and ratings within digiKam (for one test file) ... extended attributes also changed (Good) So that's reasonably clear. Need to be careful about embedded metadata when testing, it's not obvious at what point and in what situations it gets written to the file. Need to know about the "Advanced' settings and also realise that changing extended attributes is "invisible" to digiKam; it checks when it sees the timestamp changes. Equivalent run with today's build (2021-03-03) to follow.... -- You are receiving this mail because: You are watching all bug changes.
