Quote:
Originally Posted by davidfor
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. |
First things first, this has been going on ever since I got my H2O, which was pretty much around the time when it came out. Have been setting up the device numerous times with new firmware releases, fresh databases and all: no changes... (also switched computers in between, new Mac, new fresh system and everything)
then:
1. I don’t use automatic functions of the Extended Driver anymore because these kept messing up the database reliably.
2. Behavior is the same whether I eject from calibre or Finder.
3. Behavior is not occurring when I export kepubs from calibre, close calibre, then connect Kobo, then copy new books to Kobo, then eject (this causes expected database update)
4. I have disabled the „Extended driver“ and tried with regular epubs at some point, no change in behavior.
Wrap up: the USB drivers on the H2O are working somehow but they are so messed up that even slight deviation from their most basic function completely messes them up. This is basically what others in this thread have described as well. Calibre may be an additional culprit, not releasing the devices properly (in some cases) but that should not lead to unrecognized files and database corruption. (additional note: the Kindle Paperwhite I have has zero problems, the Pocketbook I used to own had zero problems, the Sony readers I used to own had zero problems).
Bottom line: this is really not to do with trying to determine what I am doing wrong but with the H2O not working properly. Ejecting USB devices from operating systems is a really basic operation that has a very simple protocol and if a device acts up while the user adheres to that basic protocol, the user is not to blame. Please don’t try!