Thread: Touch Signing out the reader
View Single Post
Old 01-24-2016, 10: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
Quote:
Originally Posted by touring View Post
Does this mean that even if there was a way to delete and replace to sqlite file, rebuilding the database would not work anyway? That the only way is to identify the dud book?
If he problem is a bad book, then the only way to fix things is to remove and fix the book.

For the errors when you tried to compress the database, the locked error usually means something else is accessing the database. Make sure you don't do this while he calibre connection jobs are running. The database or disk full error is a bit stranger. Unless the device's disk is full, or the database is very large, it's unexpected. It can mean the temp directory used when compressing the database, but that should be the devices drive, so again, unless that is full, it is not expected.
davidfor is offline   Reply With Quote