On 05/01/2021 02.00, David C. Rankin wrote:
On 1/4/21 1:04 PM, Carlos E. R. wrote:
No, it dies, and some control process starts it again (via systemd). Then it chokes and waits for some minutes, then starts again (search for <=== below)
It is probably trying to analyze files in my system that it can't. Same problem for years.
Oh..
Yep the log times show it. I see "Locale 'LANG' is not set, defaulting to C locale" -- I wonder if that figures into the issue. It says it's defaulting to C -- but how gracefully...
That's irrelevant... a red herring. I did not set the no locale thing, that was some default of the package itself. My session has a specific locale. In any case, any wrong setting, any data set that can be input to a program, must not crash a program. A program has to allow for any kind of error on the input and cope with it gracefully. If a program segfaults, that's sloppy programming and never, ever, never the user fault. tracker-extract has been crashing on this machine maybe for a decade, since it appeared. I report it, maybe they correct the problem, and then it goes crashing again on something else or on next upgrade. If you google "tracker-extract" you will see reports going back for years. I'm tired of reporting issues on it. So, does somebody really want the bugzilla? -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)