View Single Post
Old 12-11-2014, 08:13 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
I doubt if the problem was caused by the cover. To many people are using sleep covers without reporting a problem like this.

What probably has happened is that the font engine crashed. Restarting the device restarted all the software and this worked again. Why did it happen? I don't know. It could be a book related problem, a memory leak or something else. If you look in the .kobo directory, there might be a log file from when this happened. The file name will be "stack_nn.log" where "nn" are numbers. There can be up to ten of these. These, with a description of what you were doing when they were produces and possibly the book, can help Kobo developers to work out what went wrong and fix it.
davidfor is offline   Reply With Quote