Reporting Bugs
Debug logs
If you need to provide tracker logs to the developers for further study, make sure those logs are with a debug verbosity configured, or they won't be of much use.
Follow the steps in the Logging section in the Debugging page to configure all log files with debug verbosity.
- Once you configured the verbosity in the configuration files, restart tracker:
$> tracker-control -t
$> tracker-control -s <-- This step may not be needed if the distribution configures an autostart of the tracker processes, make sure NO tracker process is running before executing this. If there are already running tracker processes, don't execute it.
- Check that the logs are really showing all debug info (location may vary depending on the distribution):
$> tail -f $HOME/.local/share/tracker/tracker-miner-fs.log
$> tail -f $HOME/.local/share/tracker/tracker-store.log
$> tail -f $HOME/.local/share/tracker/tracker-extract.log
- Once you checked that the logs are in debug mode, now try to reproduce the issue you had and the one you want to report a bug about.
- As soon as you reproduce the issue, stop all tracker processes or the logs may get rotated in-place (there's a maximum file size for the log files):
$> tracker-control -t
- Finally, create a tarball with the logs and attach it to the proper Bugzilla report:
$> tar -zcvf tracker-logs.tar.gz $HOME/.local/share/tracker/*.log