View Single Post
Old 11-02-2016, 09:12 AM   #2
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
Did this happen the first time you connected to calibre after the sign-out? Were the errors before in the same line? This is happening when the collections are being fetched from the database. For some reason there is a problem with the table that holds the collections. I don't know what causes this. Not safely ejecting is about the only way I know that will do it. But, most say they do this properly, so there must be other causes.

For a corrupt database like this, unless you have a backup, the only solution is signing out. Or, dong a factory reset. As a sign out does not seem to have worked, a factory reset might be the way to go. That will reformat books partition before doing the setup again. It shouldn't be needed, but there seems to be times where it is the only thing that works.
davidfor is offline   Reply With Quote