I had a existing ~/.cache file and then upgraded to gutsy. I had to rename that file to something else so that the ~/.cache/ could be created. Before I did that, trackerd would eat all my CPU. Maybe a check to see if ~/.cache is a directory and is writeable would be a good idea, otherwise alert the user about the problem, and/or allow the user to pick a new location for the ~/.cache/ directory.
Also, before I renamed that file, running tracker-stats and tracker-status would produce worthless errors:
$ tracker-status
Tracker daemon's status is �Ë
.
$ tracker-stats
** (tracker-stats:25786): WARNING **: tracker-stats: an error has occured: Process /usr/bin/trackerd exited with status 0
I had a existing ~/.cache file and then upgraded to gutsy. I had to rename that file to something else so that the ~/.cache/ could be created. Before I did that, trackerd would eat all my CPU. Maybe a check to see if ~/.cache is a directory and is writeable would be a good idea, otherwise alert the user about the problem, and/or allow the user to pick a new location for the ~/.cache/ directory.
Also, before I renamed that file, running tracker-stats and tracker-status would produce worthless errors:
$ tracker-status
Tracker daemon's status is �Ë
.
$ tracker-stats
** (tracker- stats:25786) : WARNING **: tracker-stats: an error has occured: Process /usr/bin/trackerd exited with status 0