Created attachment 1015251 [details] Journal log fragment My Journal logs are flooded with tracker debug output that is extremely verbose, see attached example Some lines written to the log contains long fragments of the documents that are being read by tracker. I think it is enough to enable warning and error output, but there is no need to a full debug log showing INSERT actions or the data that is being manipulated.
There are more examples like: Apr 16 10:17:35 localhost.localdomain gnome-session[1461]: (tracker-extract:1827): Tracker-WARNING **: Task for 'file:///home/......image.svgz' finished with error: Could not get any metadata for uri: ... and mime:'image/svg+xml-compressed' Apr 16 10:17:35 localhost.localdomain gnome-session[1461]: (tracker-extract:1827): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: Your GStreamer installation is missing a plug-in. Missing metadata is not something should be logged on a non debug installation. a lot of files has no metadata I think log entries should be limited to critical errors, and never log the content of files unless there the verbosity is increased for debug reasons
(In reply to Robert Marcano from comment #0) > Created attachment 1015251 [details] > Journal log fragment > > My Journal logs are flooded with tracker debug output that is extremely > verbose, see attached example Those are not debug output, but warnings arising out of actual (serious) errors. > Some lines written to the log contains long fragments of the documents that > are being read by tracker. I think it is enough to enable warning and error > output, but there is no need to a full debug log showing INSERT actions or > the data that is being manipulated. Which version of tracker do you have? *** This bug has been marked as a duplicate of bug 1148570 ***
tracker-1.2.5-2.fc21.x86_64 I am attaching an ebook example, This is logged everytime I start a session
Created attachment 1015591 [details] ebook log example