Quote:
Originally Posted by davidfor
@14nc310t: I don't think BobC did anything in the database directly. He has removed the books from the device using it's interface. But, if you want to fiddle in the database, ask away. I can probably tell you what to look for.
|
Your assessment is correct - I haven't manipulated the database directly.
Quote:
Originally Posted by davidfor
@BobC: The error in your post is happening while calibre is syncing data at the first connect. Did calibre display an error dialog when this happened? The reason for the question is that the error in the post you linked to is later. It happened on the next interaction between calibre and the device. That either means the error started happening earlier, or an error was not being reported.
|
I'm pretty sure that on the occasion the log refers to the error displayed was something like "Error Communicating with Device". The error has occurred a different stages from time to time, both on initial connect and on later interaction. It is only with 2.8.1 that I started looking more closely at the logs and noticed that the error seems to occur during/after the "Update Metadata" phase. I can still get it to happen, although not every time, if I delete a book on the device from Device View. To date though an eject and re-connect has always got things going again.
Do you want the full debug log ? - I trimmed it down rather than posting the whole 10Kb.
I haven't been able to interest Kobo in the problem because it only seems to happen when the database is being manipulated and that isn't a supported activity (perhaps the desktop app does it but I don't use that as it's no good for loading the books I have). Simple book/file copying using File Manager doesn't trigger the issue.
BobC