It's unlikely there was anything in ~/.local/share/tracker causing an issue - everything in there gets erased on reindex already. I still think your issue is more likely to be that tracker-indexer is not shutting down with the daemon when a reindex is initiated. But, as I can't recreate the problem, I need someone else to help me out with that ;)
Could someone still experiencing the repeated notifications with the new version in jaunty-proposed please provide me with a log of dbus activity (dbus-monitor 2>&1 ~/dbus.log) whilst it is happening and also tell me if the tracker-indexer process terminates after each index error notification (evident by the PID changing)
Chris,
It's unlikely there was anything in ~/.local/ share/tracker causing an issue - everything in there gets erased on reindex already. I still think your issue is more likely to be that tracker-indexer is not shutting down with the daemon when a reindex is initiated. But, as I can't recreate the problem, I need someone else to help me out with that ;)
Could someone still experiencing the repeated notifications with the new version in jaunty-proposed please provide me with a log of dbus activity (dbus-monitor 2>&1 ~/dbus.log) whilst it is happening and also tell me if the tracker-indexer process terminates after each index error notification (evident by the PID changing)