View Single Post
Old 06-27-2017, 07:48 PM   #9
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
@moorekom: There was a problem reported earlier in the year with some kepub causing a reboot like you describe. I can't find the thread, but my memory says it was a problem with larger kepubs with lots of entries in the ToC. I was able to reproduce this by generating a catalogue using calibre and then converting to kepub. But, it wasn't consistent. One of my devices was OK, another failed. And another book that did it would fail the first time I opened it, but then worked after the reboot.

Are there any stack trace logs left after the reboot? These will be in the .kobo directory with the name "stack_nn.log" (the "nn" are numbers). Looking at these can help Kobo solve problems like these.

And is there any chance of seeing an example book? If it is happening with something that is free to download, then we might be able to reproduce it and work out what is happening.

Also, the Kobo Utilities plugin isn't involved in generating epubs. If you are creating them when sending books to the device, you are using the KoboTouchExtended driver.
davidfor is offline   Reply With Quote