Quote:
Originally Posted by jiembe
Sideloaded books I edit to change it to kobo.epub like all my other books. I make another serial change 2 days ago after I sent my message. Yesterday the change stand. But after receiving your post this morning, I check again and, yes, it revert to the previous serial name! And no I didn't synchronize my Kobo Glo since one week ago.
Like I said, I didn't have this problem previously. I don't remember if this problem happened before the last Kobo software update.
|
There are two ways to populate the series info on the Kobo devices. One is through the Metadata Update option of this plugin. The other is for the driver to do it automatically. There is a third, but that is only for books purchase from Kobo and synced. But, as you are only using sideloaded books, this isn't important.
The update via the plugin is only on demand. You select the books and run the function. That means the books have to be on the device and imported into the database.
The driver, if configured appropriately, will check and set the series info each time the device is connected. It will also do it after sending books to the device or deleting them. The intention of this is to make sure the series info is always correct. Plus, it was added to the driver before the Kobo Utilities plugin was created.
But, both methods get the series info from exactly the same place. The both use the standard series name and index in the calibre library. There are no options to use anything else.
What this means is that unless you changed the series details in your calibre library between connections, or running the metadata update, there is something else going on. Connecting to another calibre library with the same books but different series info would cause this.
Unfortunately, a corrupt database could also be the cause. Especially if you saw this problem after powering off the device. If the database is corrupt, then the firmware cannot update it properly. When the device needs to reread the database, such as when it is restarted, it will get old values. If this is the case, I would expect an error to be displayed by calibre when accessing the device. Whether it does, depends on the exact problem with the database, but I would expect it happen in this case. In any case, I would recommend running the database check routine in the plugin to see.
Other than this, I'm not sure what to suggest. I'd usually ask for a debug log, but if it isn't happening consistently, it would mean you need to run calibre in debug mode until it happens again. If you do, I'd like to see a log from when you update the series info and when the series info reverts.