Thread: Firmware 4.31.19086
View Single Post
Old 02-14-2022, 09:24 AM   #332
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 MGlitch View Post
Still if it were a Kobo bug you’d think we’d see much more reports of it, especially here since I’d estimate the majority of us side load. Granted as you say it’s not every time that it happens but few enough people seem to have corrupted databases that it might point to something outside of Kobo. The scan and fix message has plagued windows users for years now.

I’m curious if those having issues eject and unplug when the OS reports it safe or unplug when the Kobo goes back to the homescreen as these events aren’t always in sync with each other.
I'm not sure if I've said it before, but, my first thought on the problem is the font issues in 4.31. For me, the scan-prompt seems to be connected to adding an epub. They are imported using the RMSDK. And the cover images are rendered using the RMSDK. That means the fonts are being loaded. The way the fonts have been loaded was changed in 4.31 to try to solve an issue (you get a fallback rather than a crash). If the people are seeing this all the time use sideloaded fonts and have selected one of them as their default font, it could be the cause. Me, I use the publisher defaults, and the only reason I have sideloaded any fonts was to test the font problem.

The other thing we don't know is if they use other things such as:
  • Patches
  • NickelMenu
  • NickelSeries
  • KOReader
  • NanoClock

Or other things. Some of those will be loaded or active during the import process. I don't use them and I don't know how they interact at the times when the issues seem to happen. But, if someone is having these problems and is using them, then testing without is needed to prove it isn't them.
davidfor is offline   Reply With Quote