On 07/01/2021 00.05, David C. Rankin wrote:
On 1/5/21 5:15 PM, Carlos E. R. wrote:
I'm not very much tempted to do anything... but thanks, much appreciated :-)
If someone is really interested in correcting the source, I will help providing all the information he asks. But I don't fancy doing anything myself. I'm tired of this tracker-extract thing crashing year after year and I don't believe it is worth it :-(
See Bug 1155165, reported Oct 2019, for instance. Still "New". It is the same problem, thousands of coredumps (machine then was less powerful).
Previously I reported Bug 1123869, january 2019. That one was solved.
Chuckling...
Treat it like the dreaded-dog, shoot it in the head and be done with it. I've never needed beagle or tracker to find a file for me (but it has been tempting to find something like silver-searcher or other well behaved indexer)
I find a content searcher useful sometimes, when I can't find a file that I don't remember the name of, and it is not in the directories I expected. But it is useless if they crash and can not create the index :-(
If you were interested in trying the strace approach, I'd try editing the unit file and adding strace with, e.g.
ExecStart=strace /usr/lib/tracker-extract
At least then strace is started when tracker-extract starts. You may need to quote it, e.g. "strace /usr/lib/tracker-extract" but I'll have to defer to those better at unit file internals for that.
Interesting. Yes, I now know how to do that. The problem is adding a limit, say ten runs, or it floods the system. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)