View Single Post
Old 05-14-2021, 02:54 AM   #956
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Cootey View Post
Interesting. Since I saw no change in behavior with the removal of NickelMenu (as posted in my update), then it's probably not at fault.

A lot of these were already answered in my original and follow up posts, but here they are in one place:
  • Is the Kobo default English dictionary working correctly? YES
  • Does your Kobo directory structure look something like the attached screenshot? I use Windows. YES (I use MacOS, but the Kobo linux directory structure is the same)
  • What format is the book? epub, kepub, other? What's your Kobo firmware version? I TRIED EPUB AND KEPUB 4.26.16704
  • Is it possible the book you're using is stuffed full of soft hyphens? That would stop both dictionary and search functions from working properly. Try a different epub or kepub. I TRIED MULTIPLE EBOOKS.
  • Have your custom dictionaries become corrupt? Have you ever un-zipped then re-zipped them? If you send me a link to your Chambers/Webster zips I could try them on my Kobo to rule that out. And/or I could send you a link to the Chambers/Webster zips that I'm using and you could try those. THEY DIDN'T SEEM CORRUPT WHEN I UNARCHIVED THEM THE OTHER DAY, BUT YOUR LAST SUGGESTION IS A GOOD ONE. I'LL TAKE YOU UP ON IT.
Did you try a search of the dictionary? I don't think you mentioned this, but, can be done without opening a book. Tap the search icon, choose dictionary and the desired dictionary and search for a word. If that doesn't work, then it probably is the dictionary file.
Quote:
I've noticed other issues, however. For instance, I had screenshots enabled before I removed NM, but now I cannot disable that setting. I've loaded the config and set it to false twice since removing NM, verified that the setting is set back to false, but upon reboot screenshots are still set to true.
I don't know how NickelMenu does this. I know there is also a patch, so maybe it is happening in some way like that.
Quote:
I've deleted books remotely, which always worked before, but ghosts of them remain on my Kobo. I've corrected my account twice, but that doesn't touch sideloaded books. When I select one of these vestigial ebooks, the Kobo Clara crashes. Even though the books are not there, I still have to carefully select the three dots to remove them (otherwise the book is selected and kaboom).

I'm thinking of nuking it from orbit. It's the only way to be sure.

If after a factory reset, I *still* have problems with the dictionary, I'll definitely have you look over those files and try out yours.

I've never had a Kobo misbehave quite so badly before. Something must be corrupt. Frankly, I blame Ultimate Manga Reader which crashed my Kobo so numerously last weekend, I had to disable it so that I didn't accidentally select it again.
All that sounds like a corrupt database. By "corrected my account", do you mean the "Repair your Kobo account" in settings? That is mainly fixing issues with purchased books. I shouldn't go near sideloaded books. And it probably doesn't do anything if the database is corrupted. Or it might, but, the fixes probably won't get saved to the database properly.

Signing out of the account and back in usually fixes it. That recreates the database. And factory reset should definitely fix it, but, is usually overkill. Though you sound like you might be in the mood to do just that If you do a factory reset, do it from the Developers options or the external method. These wipe the root partition and reinstalls the factory firmware. The method from the Device information doesn't do that.
davidfor is offline   Reply With Quote