https://bugs.kde.org/show_bug.cgi?id=389692
--- Comment #7 from Méven Car <meve...@gmail.com> --- (In reply to Serg Podtynnyi from comment #6) > It might be all wrong, but some time ago I researched a little bit about > XAttr problems in Dolphin/Baloo, and my findings points that Baloo file > watcher service doesn't pick up the changes made by dolphin and don't fire > `metadate` update. I attached to dbus monitor and did not saw the events for > xattr changes , also it might be some inotify limitations of how many files > that can be monitored by file watcher. Definitely this can be researched > more. Baloo watches the directory it is directly configured to index (function FileWatch::watchFolder), but it does not have the capability to watch on whole filesystem ATM or watch for directory creation which would allow it to recursively set watch (it would need to use fanotify, with a dedicated daemon for instance). KIO/KCoreDirLister does not provide Xattr but monitors all the files dolphin displays. It could be extended with some effort to support them, it does copy them already. And to add to the knowledge, KFileMetaData has the necessary bits to read/write xattr cross-platform, it is used in baloo. A possible workaround, would be to relay xattr changes that dolphin receives from KDirLister and the file force-index using baloo. Not sure if currently dolphin does receive notifications when xattr changes ATM though. -- You are receiving this mail because: You are watching all bug changes.
