https://bugs.kde.org/show_bug.cgi?id=433822
--- Comment #4 from [email protected] --- Thank you for the replies... > ... Baloo has brought us many bug reports with crashes > over the years ... I don't think I was using it in the bad years. Now, from my perspective, I think "hat's off". It's an incredibly messy and challenging project. My feeling here is that digiKam is reading/writing xattr on the filesystem, the data you can see with "getfattr -d". Baloo reads this data, digiKam can read and write this data. For this bit of the work it _seems_ the two are independent. > ... you can switch off reading of the rating tags in the > advanced metadata settings ... It could be that I've written changes done within digiKam back into the embedded metadata, and digiKam is reading this info in preference to (modified) extended attributes. I will check. I am happy to carry on troubleshooting As an initial suggestion. If people see: Read metadata from Baloo there'll be an expectation that digiKam will try to read the info. Could there be an option in the advanced settings, to show xattr as a source - and list things like user.baloo.rating, user.xdg.tags etc explicitly, although by default unchecked, at the bottom of the list? Further on perhaps, if "Read metadata from Baloo" is selected, these options could be checked -- You are receiving this mail because: You are watching all bug changes.
