GNOME Bugzilla – Bug 730083
EPub extractor generates many "No member '...' in zip file" warnings
Last modified: 2021-05-25 17:53:41 UTC
[adamw@adam ~]$ tracker-control --get-log-verbosity Components: Store : errors Extract : errors Writeback: errors Miners (Only those with config listed): Files : errors However: [adamw@adam ~]$ sudo journalctl -b | grep tracker-extract | wc -l 1423 [adamw@adam ~]$ sudo journalctl -b | grep tracker-extract | grep "Tracker-WARNING" | wc -l 1423 i.e., all those 1423 log entries are "Tracker-WARNING" messages. Why are these being logged when the log-verbosity is set to 'errors'? Note I have not manually changed log verbosity at any point, I am using tracker 'out of the box' here. A lot of the errors seem to be problems with interpreting epub files (or possibly bad epub files?): Apr 25 13:52:40 adam.happyassassin.net gnome-session[2210]: (tracker-extract:2690): Tracker-WARNING **: No member './Oath_of_Fealty_split_058.html' in zip file 'file:///home/adamw/Documents/books/Elizabeth%20Moon/Elizabeth%20Moon%20-%20Legend%20of%20Paksenarrion%2006%20-%20Paladin's%20Legacy%2001%20-%20Oath%20of%20Fealty.epub' but I wouldn't expect these WARNINGs should be logged at log verbosity level "errors" anyway. This doesn't seem to be new to 1.0.1, now I check, I seem to have it with 1.0.0 also.
Filed the actual issue causing the warnings (handling of epub files) as https://bugzilla.gnome.org/show_bug.cgi?id=730085 .
When set to "errors", that means ANYTHING that's higher importance than G_LOG_LEVEL_MESSAGE. That includes warnings, errors, criticals, etc. technically warnings are an error of sorts. They shouldn't happen. The difference is really how severe the error is. Out of interest what level would you expect these to be logged at?
hum, i'd usually expect 'warning' and 'error' to be different loglevels - typically you see something like 'error', 'warning', 'info', 'debug' in that order, i.e. loglevel 'debug' will log everything, loglevel 'info' won't log 'debug' messages, loglevel 'warning' won't log info or debug messages, etc etc. But if it's as designed, I'm not gonna argue much...though as a user having thousands of these messages in my logs isn't really doing anything to help me.
Hi guys, Im seeing the same behaviour. $sudo journalctl -b | grep tracker-extract | wc -l 7400 $ sudo journalctl -b | grep tracker-extract | grep "Tracker-WARNING" | wc -l 7389 looks like this is reported here a few times: Bug 750309, 747198 ... Is there a workaround? or progress with this? Thanks Dean.
Some work has gone into fixing this, I am not sure if you have the latest version, but these fixes are in place already: bug #735406 bug #746256
I suspect bug 746437 fixes this issue. It has a patch which is yet to be committed.
I can confirm that this was my issue. Im running 1.4.0-3 now and epub's are indexed without error (Im seeing other complaints now but ill worry about that another day ;-) Thanks for all your hard work