Thread: Elipsa Ghost eBook Purchase on an Elipsa
View Single Post
Old 08-24-2021, 05:36 AM   #37
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 have done some playing and can reproduce the database corruption when CBZs or CBRs are involved. Basically, if I have read a comic and connect to a PC and then do anything that updates the database while connected, I can end up with a corrupted database. It doesn't happen all the time. As it is happening when the database is updated, using calibre will do it. But, so will using the Kobo desktop application. Both can update the database and that clashes with whatever hasn't stopped using the database when the device was connected.

There is nothing that can be done from calibre. I don't think there is any way to detect if something is still using the database in this way. There are two operating system involved, and no way for them to communicate.
davidfor is offline   Reply With Quote