View Single Post
Old 12-17-2012, 01:13 AM   #3
brudigia
Evangelist
brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.brudigia ought to be getting tired of karma fortunes by now.
 
Posts: 491
Karma: 1401828
Join Date: Oct 2008
Location: Torino - Italy
Device: iPAD AirPro M1 12.9, Kindle Scribe, Kobo Elipsa, iPhone XV
Quote:
Originally Posted by davidfor View Post
HI Bruno.

The errors tell me there is a problem in getting the collections for a book on the device. For the Kobo devices, the collections are made up of the shelves, the reading states (Im_Reading, Finished and Closed) and a collection each for "Previews' and "Recommendations". This should work when the only books on the device are kepubs. But, I'm not sure if I have ever tried this.

Finding and displaying the same nine books makes sense. The error is either in the ninth book or the tenth the driver finds on the device. To find the books, the driver is reading a database on the device. This will always be read in the same order. Without looking at the database, I can't tell which books would be the ninth and tenth.

I suspect that the second error is happening at another time but is not being displayed.

A few questions:

- What firmware version is the Glo running?

- Have you created any shelves on the Glo?

- What do you have the save template set to in the device configuration?

- After the error when sending books to the device, are the books on the device when you disconnect it? Does the processing sceeen show when you disconnect and do they show in the devices library list?

I would like to see a debug log. This should show me when the error first happens. To do this, after starting calibre, restart it in debug mode by pressing CTRL+SHIFT+R or selecting "Restart in debug mode" from the preferences menu. When calibre restarts, it show a message about the debug log. Then connect the Glo, wait for calibre to do the sync then do whatever causes the error. After that close calibre. Once it is closed it will open a log file. Post or send me the log file.

After giving me the logs, I can think of two possible workarounds that might get books onto the device:

- In the calibre preferences on the "Sending books to devices" page, change the "Metadata management" option to manual. This has to be done without the device connected. This should prevent the error you are seeing when you send a book to the device.

- Instead of using "Send to device" use "Save to disk" to get the book on the device. Saving the book to the drive the device appears at will bypass the error on the send.


David
Thank you for your answer.
As for your questions:
- the kobo has the firmware 2.1.5
- no, I did not create any shelves the Kobo, but I found there were the same shelves I have on my PC Kobo app. When these shelves were created, I do not know, they could have been created by the app. I failed to notice.
- the save template is the standard one, {author_sort}/{title} - {authors}
- I am not sure I completely understand the last question. I have tried transfering a book on the Kobo (Calibre Library, right mouse button, move to device) and I get the second message. Luckily it is not a blocking error. After, it seems that the book is on the device, although Calibre does not seem to notice.

Thanks for the time taken to answer. Hope it helps. I shall try what you have suggested and let you know.

EDIT : I started Calibre in debug mode. I stand corrected, as the books show up in the calibre library as being on the device, when I transfer them. I will now try to look onto the device.......
Unfortunately in this case, as before, Calibre enters a loop out of which there is only one way, stopping it in the task management.
I shall pm you the log. THanks again.

Last edited by brudigia; 12-17-2012 at 01:21 AM. Reason: Started Kobo in debug mode
brudigia is offline   Reply With Quote