Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 06-22-2020, 10:53 AM   #2236
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 jgoguen View Post
If it's metadata it may not be this driver. Can you do a few things:
  • Remove all problematic books from the device
  • Restart calibre in debug mode
  • Send one single problematic book to the Kobo, then close calibre (to get the debug log) and restart it normally
  • Attach a scrambled copy of the book and the calibre debug log
Based on @jxall's post, the problem is not the driver. It seems to be happening when kepubs are sent from the library. It looks like a problem with the KePub Metadata Writer plugin. It is writing a zero length OPF file when I do a conversion or use the Embed metadata tool. That will happen with the send-to-device if there is a kepub in the library.
davidfor is offline   Reply With Quote