Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 10-06-2017, 09:34 AM   #1727
mathil
Evangelist
mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.mathil ought to be getting tired of karma fortunes by now.
 
Posts: 445
Karma: 287725
Join Date: Sep 2014
Location: Europe
Device: Kobo Aura H2O/Glo HD/Libra 2, Kindle PW3/PW5/PW11, Boox Palma
Quote:
Originally Posted by davidfor View Post
Firstly, this has nothing to do with the device firmware version. Plugin installation does not check the devices and if the device is not connected at the time, calibre has no knowledge of what devices you have.

There shouldn't be a problem with the driver. It is working for me under calibre 3.8.0 and I have seen no problems. This sort of error usually means the zip file for the plugin has been corrupted. Or someone has repackaged it incorrectly. What I would do is check in the calibre configuration directory and look for anything strange in the "plugins" directory. If there is a file for the driver. The file name is "KoboTouchExtended.zip". Do this with calibre not running.

If this doesn't fix it, run calibre in debug mode (right-click the preferences button) and do the install. Then close calibre and post the log that gets displayed. Hopefully that will show more about what is going on.
Thank you for your reply, davidfor I followed your suggestion: the plugin folder had nothing strange inside, and no file for the driver. After checking this, I opened Calibre in debug mode and the driver install worked as it should; rebooting it in regular mode shows it's still there. Everything seems to be working as it should now. I'm not sure exactly what happened... but thank you for your help!
mathil is offline   Reply With Quote