Thread: Kobo Firmware 3.5.0
View Single Post
Old 07-18-2014, 10:53 PM   #209
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 GeoffR View Post
It's the only thing I could think that would cause the effect anacreon saw, but I'm not going by experience, I've never had a corrupt database.
Yes, this behaviour could be explained by the content_settings table or an index being corrupted. If it was just that table, then most things would work. If it is, then as jackie_w said, it usually means a death spiral until it dies completely.

anacreon: Run a check on the database to see if it has any problems. You can do this from a SQLite manager, or the Kobo Utilities plugin in calibre.
davidfor is offline   Reply With Quote