Thread: Collection being wiped from my Libra
View Single Post
Old 09-25-2020, 11:22 PM   #5
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 Uncle Robin View Post
I have made no changes at all to my Calibre configuration, it took me several minutes to even FIND the the drivers you mentioned. It turns out that both plugins are enabled. I've made sure collections aren't selected in either, but how do I know I know which one is being used, and what are the differences between them?
If both are enabled, then the KoboTouchExtended driver will usually be used. It's primary purpose is to transform epubs into kepubs when a book is sent to the device. It shares most of the code with the built-in KoboTouch driver, so most of the function is identical. The differences are nearly all related to the creation of the kepubs

To see which is actually used, connect the device. Then, right-click the device list button and select the option to configure the device. This will open the configuration dialog for the active driver. The Kobo Utilities button will also show the active driver, but, it assumes only one is active so it might get it wrong.

Was the collection management configured for either driver? If so, that was probably the cause of the collections being emptied. If it wasn't configured, then I don't know what is happening. You can run calibre in debug mode and post the log for me to look at. This can be done by right-clicking the preferences button and selecting the option to restart in debug mode. Calibre will restart and display a message about the log. Connect the device and let the connection jobs run. When they are finished, close calibre and the log will be displayed. Post the log, or PM it to me.
davidfor is offline   Reply With Quote