View Single Post
Old 06-02-2019, 12:02 AM   #1616
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 ICDeadPpl View Post
I get this error when Calibre tries to update metadata and upload queued books from the Reading List plugin, when I connect the reader to my Windows 10 computer:

Code:
calibre, version 3.44.0
ERROR: Error: Error communicating with device

local variable 'ContentType' referenced before assignment

Traceback (most recent call last):
  File "site-packages\calibre\gui2\device.py", line 89, in run
  File "site-packages\calibre\gui2\device.py", line 542, in _sync_booklists
  File "calibre_plugins.kobotouch_extended.device.driver", line 481, in sync_booklists
  File "site-packages\calibre\devices\kobo\driver.py", line 969, in sync_booklists
  File "site-packages\calibre\devices\kobo\driver.py", line 2435, in update_device_database_collections
  File "site-packages\calibre\devices\kobo\driver.py", line 643, in get_content_type_from_path
UnboundLocalError: local variable 'ContentType' referenced before assignment
I'm on firmware version 4.15.12920 on my Kobo H2O.
That is an error due to some work being done on getting calibre code ready for Python3. It will be fixed in the next release. But, I'm surprised this didn't cause a problem before. I'd like to have a look at what is happening. Could you run calibre in debug mode and post or PM me the log? You do this by right-clicking the preferences button and select the restart in debug mode option. Then connect the device and let the connection jobs. When they finish, which will probably be when the above error happens, close calibre and the debug log will be show. Send me that via post or a PM.

Also, this isn't an issue with this plugin. It is the driver and should be separate from here.

Last edited by davidfor; 06-02-2019 at 12:04 AM.
davidfor is offline