View Single Post
Old 06-12-2021, 05:58 AM   #3
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
Firstly, it is not the firmware. This is not considered at all in either a conversion to kepub or when sending to the device using the KoboTouchExtended driver. Plus, the last firmware release was in February. If it was that, it would have started then.

The problem is most likely errors in the books you are sending. If you open the book in the editor and run the check book tools, any errors shown can break the transformation that the KoboTouchExtended driver does. I hit this for the first time in a while this week. There was an error in the ToC and it needed to be fixed to get it on the device. But, as @PeterT said, we need to see a debug log to get an idea of what is happening. Or a conversion log from the conversion to kepub.
davidfor is offline   Reply With Quote