Arch Linux

JayDoe

Member

Registered: 2014-09-20

Posts: 27

tracker-extract spam in system log

Hi,
I recently moved from Ubuntu to Arch. On both distribution I use Gnome 3. I took my home directory from Ubuntu to Arch.

Now I get a couple of Gnome warnings and errors in my system log, especially from the tracker-extract. For every file, which was failed indexing, I get a warning like this:

gnome-session[1488]: (tracker-extract:1620): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: Ihrer Installation von GStreamer fehlt ein Plugin.
gnome-session[1488]: (tracker-extract:1620): Tracker-WARNING **: Task for 'file:///home/JayDoe/Documents/somefile.xcf' finished with error: Could not get any metadata for uri: 'file:///home/JayDoe/Documents/somefile.xcf' and mime:'image/x-xcf'

... and the same for different filetypes. For a few of them, I'm sure that there's no gstreamer-plugin for it, since they're from special software and I only keep it as a part of a project, I don't want to work with them on this machine.

So after checking, that I have gstreamer and gstreamer0.10-plugins installed, I try to use the tracker-preferences, to ignore these file types. In the preferences gui, I added '*.xcf' in the to ignore list. But the warning still appears.

How can I reduce the log-level of the tracker? I think, wrong indexed files can appear quite often and I dont want the tracker to spam my system log, so I may can miss some important messages.. For every boot it's about 80-90 lines of messages from the tracker...

Hope you can help me, thanks

bye
JayDoe

flittermice

Member

From: Vienna

Registered: 2013-09-07

Posts: 14

Re: tracker-extract spam in system log

This drives me crazy, too. There are many file types on my computer that make these messages appear (mdb, raw, xcf, ...).

In addition there is on e-book on my HD whis causes tracker to write tons (approx. 300 lines) of text into the journal (it looks like a SQL dump): http://pastebin.com/wQ6hkEY1
I have not read the book yet but i regularly can read one or two pages of it when I examine the journal :-/

I've tried to find some information on the Gnome site, but Tracker seems to be undocumented at all.

garnacho

Member

Registered: 2015-03-11

Posts: 2

Re: tracker-extract spam in system log

This drives me crazy, too. There are many file types on my computer that make these messages appear (mdb, raw, xcf, ...).

In addition there is on e-book on my HD whis causes tracker to write tons (approx. 300 lines) of text into the journal (it looks like a SQL dump): http://pastebin.com/wQ6hkEY1
I have not read the book yet but i regularly can read one or two pages of it when I examine the journal :-/

I've tried to find some information on the Gnome site, but Tracker seems to be undocumented at all.

Here goes a wild idea: File bugs!

Tracker has plethora of documentation, both in the gnome wiki ( https://wiki.gnome.org/Projects/Tracker … rch=Titles ) and installed as API documentation (which you can see in devhelp)

Both the attempt to extract unrecognized formats and the insertion error in the pastebin (we don't dump stuff to stderr just because) are bugs. But hey, we perhaps wanted to drive you crazy, it drives me crazy too to stumble upon otherwise valid bugs in random forums.

flittermice

Member

From: Vienna

Registered: 2013-09-07

Posts: 14

Re: tracker-extract spam in system log

Dear garnacho,

here's the bug: https://bugzilla.gnome.org/show_bug.cgi?id=746256
Thanks for the information about the documentation.

flittermice

garnacho

Member

Registered: 2015-03-11

Posts: 2

Re: tracker-extract spam in system log

Dear garnacho,

here's the bug: https://bugzilla.gnome.org/show_bug.cgi?id=746256
Thanks for the information about the documentation.

flittermice

Thanks, much appreciated. Some fixes have gone in 1.3.6.

The epub error in http://pastebin.com/wQ6hkEY1 is different though. It would be great if I could get the epub file as a local testcase, if you don't have copyright concerns too. I've changed the profile to show my email, It'll go from there directly to a local testing folder.