Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 05-27-2020, 01:11 AM   #2118
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 Dfaure View Post
Could someone confirm that the KoboTouchExtended is the only Kobo related plugin affected by the reported bug?

I was wondering if this apply to the KePub dedicated ones since they got the same release number...
There is shared code between the extended driver and the kepub related plugins. Errors in one might appear in the others.

But, in this case, I'm pretty sure that the problem is that you are running this under Python 3.8. The error is in one one the recent changes in the plugin to use a calibre supplied function. That is probably failing as the Python 3 version of calibre is still a work in progress. And it probably means the other plugins will fail in the same way.

A basic rule for calibre is don't use the distro version. They can work, but, eventually a problem comes up. Like this.
davidfor is offline   Reply With Quote