Quote:
Originally Posted by Aldous04
That was the output I got in the command prompt when I ran the 'run.cmd' from the 'Annotations-Kindletest' folder. I assumed that was what you meant by log as I can't see a log file generated anywhere. This is the error I get when trying to fetch annotations from my Kindle: Spoiler:
calibre, version 2.7.0
ERROR: Unhandled exception: <b>MobiError</b>:Unknown book type: c??}???
calibre 2.7 isfrozen: True is64bit: False
Windows-7-6.1.7601-SP1 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '7', '6.1.7601')
Python 2.7.8
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Successfully initialized third party plugins: Marvin XD && iOS reader applications && Annotations
Traceback (most recent call last):
File "calibre_plugins.annotations.action", line 333, in fetch_usb_device_annotations
File "calibre_plugins.annotations.action", line 522, in get_annotated_books_on_usb_device
File "c:\users\user\appdata\local\temp\calibre_annotati ons_plugin\Kindle.py", line 168, in get_installed_books
File "c:\users\user\appdata\local\temp\calibre_annotati ons_plugin\Kindle.py", line 264, in _get_metadata
File "site-packages\calibre\ebooks\metadata\mobi.py", line 493, in get_metadata
File "site-packages\calibre\ebooks\mobi\reader\headers.py", line 273, in __init__
File "site-packages\calibre\ebooks\mobi\reader\headers.py", line 301, in identity
MobiError: Unknown book type: c??}???
|
Yes, that's the same error.
Quote:
|
I'm not sure what I'm supposed to see when I run in debugging mode; I get the same 'MobiError: Unknown book type: c��}�ݛ�' as above, without any additional information. Am I supposed to be looking for a log.txt?
|
You can run calibre in debug mode in two ways. One is from inside calibre. You right click on the preferences button in calibre and select "Restart in debug mode". Calibre will restart and display a message about a log file. When you close calibre, it will display the log file to you. The other way to do this is to run the command "calibre-debug -g" from the command line. That will display the messages in the command window while calibre is running. This will only display the last few messages depending on how big the window is.
But, before doing either of these, open the annotations configuration and select "Enable debug logging for Annotations plugin". This will write extra messages from the plugin to the debug log. The version of the plugin I posted recently has some extra logging to show the file name of the book that is causing this error.