View Single Post
Old 07-27-2020, 05:10 PM   #2
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
I just fixed a sneaky issue that broke name resolution in some specific circumstances on Kobo, that could theoretically trigger what you've seen (especially if a local catalog, e.g., Calibre's, works just fine). Then again, you probably wouldn't have been able to even *browse* the catalog, first, so, eh.

You could try switching to today's Dev nightly, and then see if it works any better after a full device restart, and not running any other third-party code before, because they might all suffer from the same quirk, since they tend to take inspiration from KOReader's Wi-Fi scripts.

(That was a long winded way to say that I can't reproduce this on the current nightly ^^).

If the current nightly doesn't fix it, open an issue on GitHub with a *debug* (Tools > More Tools > Dev options > Debug logging) crash.log attached.

Last edited by NiLuJe; 07-27-2020 at 06:05 PM.
NiLuJe is offline   Reply With Quote