View Single Post
Old 04-22-2021, 10:57 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 Filmbrain View Post
I did eject safely, but what I did notice is that the Kobo didn't do the usual post-eject "Importing new content" (or whatever the message is.) I thought because I had deleted and replaced the same book with the same file it wasn't necessary, so I didn't think much about it. Then when I plugged it in the next time I had the problem.
As I said, it should work and does work here. When you delete the book using calibre, it should remove the database entries for the book. And after the eject, it should detect there were changes and import the book as a new one.

What happened after you ejected suggests either you didn't do the delete first (I know I frequently forget what I have and haven't done when fiddling with these devices) or the database corruption had happened by this point. Unfortunately, it is probably impossible to work out what actually happened and caused the problem.
davidfor is offline   Reply With Quote