View Single Post
Old 03-09-2021, 07:57 AM   #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
Firstly, unless you are using the metadata update function of the Kobo Utilities plugin, it is not involved here. And if you are using that function, check the options when you do the update.

The KoboTouch and KoboTouchExtended driver can both update the metadata on the device when you connect it. This can be turned off if you want. But, it does this using the plugboard. You should get the same results when the book is sent and when the device is connected the next time.

To see what is happening, I need to see a debug log. Firstly, go into the driver configuration and on the third tab, in the "Title to test when debugging" field, put the title of a book on the device that is showing the problem. Then, restart calibre in debug mode (from the preferences menu) and then connect the device. When the connection jobs finish, close calibre and the debug log will be displayed. Post the full log, or upload it somewhere and PM me the link. Hopefully I'll be able to see the problem.
davidfor is offline   Reply With Quote