GNOME Bugzilla – Bug 741583
tracker-miner-fs fails when a file is renamed
Last modified: 2014-12-16 16:23:15 UTC
Using tracker 1.2.4, when a file is renamed, the file system miner will print out a critical warning, and fail to update the index for that file. This is the warning: (tracker-miner-fs:2392): Tracker-CRITICAL **: (Sparql buffer) Error in task 0 of the array-update: Subject `(null)' is not in domain `nfo:FileDataObject' of property `nfo:fileName' (tracker-miner-fs:2392): Tracker-CRITICAL **: Could not execute sparql: Subject `(null)' is not in domain `nfo:FileDataObject' of property `nfo:fileName' I found a reference of this very same error message in this commit by Sam: https://mail.gnome.org/archives/commits-list/2014-August/msg06580.html
This seems to only happen for regular files, and not for directories.
Created attachment 292800 [details] [review] patch This patch seems to fix it for me, but I am not 100% sure of the approach. Rationale in the commit message - comments welcome!
Thanks for the patch! As you noted, I also spotted, but failed to fix (or report) this issue .. Looks like https://git.gnome.org/browse/tracker/commit?h=68559df979fe70c4d473026354fe963407fa5db7 introduced this bug, and I guess that setting 'force = TRUE' is effectively just reverting the behaviour back to how it was before, so shouldn't have any serious performance implications.
I have a strong suspicion this bug 678986 is related and the patch(es) there are a more comprehensive solution. I believe Philip and I are waiting on Carlos for input before committing. Thanks Cosimo.
Oh indeed - my patch is actually exactly the same of https://bugzilla.gnome.org/attachment.cgi?id=289394 which is marked as accepted-commit_now :-) Closing as a duplicate. *** This bug has been marked as a duplicate of bug 678986 ***