View Single Post
Old 03-04-2011, 04:40 PM   #8
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
The problem is that the traceback makes no sense.

The line "File "site-packages\calibre\gui2\device.py", line 383, in add_books_to_metadata" refers to real code in 0.7.47, where the device driver is called. However, the line "File "<string>", line 372, in add_books_to_metadata" refers to nothing, and the line number makes no sense for the kobo driver. First, the <string> indication means that what is running is *not* part of calibre,. Second, that line number is not inside add_books_to_metadata, and the file name of <string> indicates that something bizarre is happening.

Have you installed a different driver, perhaps as a plugin? Have you installed calibre source? Have you put a driver in calibre's installation folder? You have clearly done *something*.

In any event, it is clear that you are not running a standard calibre release. Why that might be is a mystery, and one that we cannot solve. Only you know what the history of your installation is.
chaley is offline   Reply With Quote