View Single Post
Old 06-24-2016, 07:54 PM   #7
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
The errors are in code that reads the settings. I think what is happening is that the configuration for the driver was damaged during the initial attempts to use it. Now there is something in it that is preventing it from being read properly.

The fix should be to delete configuration file. This is in the calibre configuration file and is called "device_drivers_KOBOTOUCHEXTENDED.py". Unfortunately, you will need to redo the configuration before connecting the device.

For the collections, did you check the KoboTouch driver configuration before using it? If you used the driver for collection management in the past, the configuration could still be there and has come into affect now.
davidfor is offline   Reply With Quote