Quote:
Originally Posted by davidfor
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.
|
So this is a Kobo issue where something is left open in the database when comics are involved? It's not closing access to the database properly? I've been ripping my hair out over here, and talking to tech support doesn't help. They just have me wipe everything and start over which "fixes" the database issue until I randomly read a comic while the moon is over Mars while the wind blows southwesterly. I'm glad you two have been able to quantify better what is happening. I suppose the problem could happen with the Kobo desktop, but I haven't noticed it. It only happens with Calibre for me. Reading manga on my Elipsa was one of the reasons I got it. I'll have to remove them all in the interim.
Will you be filing a report with Kobo? I can use their website to leave feedback, but as a customer, my experience is that they just assume I'm an idiot who doesn't know one end of the Kobo from the other.