Hi Chris On 4/15/17, Chris <[email protected]> wrote: > I've asked about this several times and have received, that I'm aware > of, no replies. Not even one saying 'don't worry about it'. If a bug > report is necessary I'd be happy to submit one. Here is what the latest > shows in my syslog (please ignore other than the pertinent entries). > > https://pastebin.com/rWpuwgEJ >
Sorry for the lack of responses about this. I think this error occurs when the tracker-miner-fs tries to insert duplicate information for files that are already in the store. That's why the error says "UNIQUE constraint failed": the nie:url table enforces that there's only one entry for a given URL, so the duplicate insert is rejected. This error is mostly harmless, but obviously it's bad that Tracker is wasting energy trying to insert duplicate entries to the database and filling your syslog with junk. I've seen this before but I don't know what causes it. I guess we need to add more diagnostics to tracker-miner-fs so that it gives more useful error output; it's the sort of problem that never occurs when you're actually in a position to actually debug it. It's possibly a compatibility issue caused when upgrading from one version of Tracker to another ... (our automated tests don't cover that at all at present sadly). I hate recommending this but I think that removing the database and recreating it will fix. If you don't have important data saved in your Tracker database try `tracker reset --soft`, and if that doesn't fix, `tracker reset --hard`. There appears to be no bug for this already in Bugzilla, so please file one if you can. And thanks for contributing to Tracker! Sam _______________________________________________ tracker-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/tracker-list
