Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 12-21-2021, 09:29 PM   #2638
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 ownedbycats View Post
I got my Kobo Libra H2O. The first few times connecting & sending books went fine. Then I plugged it in again and got this:

Code:
'utf-8' codec can't decode byte 0x83 in position 637: invalid start byte

Traceback (most recent call last):
  File "calibre\gui2\device.py", line 87, in run
  File "calibre\gui2\device.py", line 512, in _books
  File "calibre\devices\kobo\driver.py", line 1988, in books
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x83 in position 637: invalid start byte
Switching to the regular driver works, but I prefer kepubs. I checked the database and it's good. Any idea what I'm doing wrong?

EDIT: Attached debug log.

ANOTHER EDIT: I noticed the KoboTouchExtended settings was a lot of null characters in the debug log. So just to see what happened i moved the device_drivers_KOBOTOUCHEXTENDED.py.json file out and re-created all the settings. Now it's working. I've attached the old json (renamed to txt because of file upload limitations) for investigation.
All I can say to that is that it is weird. I can see the strangeness in the logs, but, I can't see anything in configuration file that would be causing this. The other times I have seen this problem, it seemed to be an unusual character in one of the fields pulled from the database. But, I've never worked out how it got there or exactly what it was.
davidfor is offline   Reply With Quote