Thread: Libra Kobo Libra factory reset itself?
View Single Post
Old 12-04-2020, 07:44 AM   #17
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 retro View Post
Not sure why you keep attacking me for saying the Bookreader.sqlite is being corrupted. When I delete the old one and the Bookreader.sqlite-shm and .sqlite-wal files left behind and copy my backup over, the error goes away and I do nothing to the koboreader.sqlite. The only thing I use to access it is calibre or explorer. Perhaps it something else corrupting it, but it is being corrupted and calibre throws the error.
As I keep saying, calibre has absolutely no knowledge of the Bookreader.sqlite file. It doesn't attempt to open it because it doesn't know it exists. As the source is available, it is dead easy to prove that. There is no way that calibre is corrupting that file. And there is no way that that file being corrupted could cause an issue with calibre. The only possible way would be if that file is somehow causing a file system error. And if that is the case, you have a lot bigger problems than a corrupt database.
davidfor is offline   Reply With Quote