Quote:
Originally Posted by johnnyb
Do you also have a Mac? Are you using calibre? Are you using the Kobo extension plugins? Are you using kepub?
For me, the problem is especially pronounced in connection with calibre. It does not seem to want to let got of my Kobo, hence the failed ejections. What Kobo could actually do is let users update the database manually (some “search for new books” button that essentially simulates a proper “eject-search for files-add new files to db-refresh display” sequence) and try to make their readers less sensitive to atypical ejection. Sometimes, upon ejecting, my H2O reverts to its home screen as if nothing happened and I only realize that it hasn’t loaded the database properly is because it won’t let me delete tiles anymore. If I then start reading are deleting files or anything that is written to the database, I risk messing it up.
|
With that description, the problem isn't the device being ejected. The problem is whether the database was closed properly by whatever had it opened. So...
- What happens if you don't use calibre? Just connect and manually copy books to the device? Or disable the driver and use save-to-disk or connect-as-folder?
- What happens if you close calibre and eject using the the Mac tools?
- What happens if you connect, wait for the initial jobs to finish and then eject?
- What happens if you wait a few minutes after calibre finishes its jobs that access the device?
- By "Kobo extension plugins", I assume you mean my Kobo Utilities plugin. If so, what functions of it are you using every time you connect? What if you don't use them> Do you use the automatic backup?
- You mention kepubs. I doubt that is significant in itself. But, are you using the extended driver? That has one extra database update that the main driver does not have. That should not be used much unless you are sending a lot of books that the device cannot generate cover images for.
- Has this changed recently? I changed the Python SQLite library and restructured some code. This would have been in calibre 2.63.
The last thing is, how long has this been going on? Until this thread, I can't think of any Mac issues being reported for a while. The last issue I can think of was a version of Mac version that didn't recognise the devices properly. Maybe I have missed something, but I'm sure I haven't seen any mention of this.