View Single Post
Old 12-09-2018, 09:08 PM   #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
That is failure when the driver is updating the metadata on the device. It will mean that the metadata was not updated for that book or any after it in the list. It shouldn't be a big problem as the next time the device is connected the update should happen. And other functions probably worked as the database lock was probably released by the time they happened. And sending books should fail in such a way that the book is put on the device, but other changes aren't made.

But, the real question is why the database was locked. Were you doing anything else at the time? Such as running something from Kobo Utilities? Or something else that looked at the database? The latter would include the Kobo desktop application.
davidfor is offline   Reply With Quote