Quote:
Originally Posted by davidfor
Is this with calibre 3.35? I saw something like this while doing the recent changed, but, I thought I had fixed it. I'll have another look at it. But, a debug log from the connection should be useful.
To let me see what is happening, in the driver configuration, put the name of the errant book in the "Title to test when debugging" field on the third tab. It doesn't need to be the full title, just something that will match the book without matching to many others (i.e. don't use "the"). Then run calibre in debug mode (right-click the preferences button and select "Restart in debug mode"), let the device connection jobs run and then close calibre. Calibre will display the log. Then post or PM the complete log to me.
|
3.35 But it must have been cockpit error. I ran Kobo Utilities Update metadata on the 3rd connect.
I am new to Kobo, I expected it to just happen on the second connect
