[GUI Plugin] Kobo Utilities

[Usered]

I just deleted the file you mentioned and everything works fine now, thanks!

[Usered]

Well I spoke too soon, now when I plug in my kobo I get this: failed to backup device database

calibre, version 7.12.0 (win32, embedded-python: True)
Failed to backup device database: Non riuscita: Backing up Kobo device database

[Errno 13] Permission denied: 'D:\\Backups\\Kobo\\KoboReader-KoboLibra2-N418170017590-20240602-182748.sqlite'

Traceback (most recent call last):
File "calibre\gui2\device.py", line 111, in run
File "calibre_plugins.koboutilities.jobs", line 199, in do_device_database_backup
File "shutil.py", line 258, in copyfile
PermissionError: [Errno 13] Permission denied: 'D:\\Backups\\Kobo\\KoboReader-KoboLibra2-N418170017590-20240602-182748.sqlite'

[Usered]

Originally Posted by Usered

Well I spoke too soon, now when I plug in my kobo I get this: failed to backup device database

Ok, solved this by creating a new backup destination folder, the previous one was somehow non-existent.

[JSWolf]

Originally Posted by theducks

Make sure you are up to date on both Calibre and the Kobo plugins.
Plugins sometimes need to keep up with major Calibre changes.

FWIW it works on W10 Calibre 7.12

Works on Windows 12 with calibre 7.12 as well.

[rb431]

I can't seem to run any firmware newer than 4.35.20400 on my Forma. I have 2.16.13 of the plugin installed into Calibre 7.12 running on Windows 11. This has actually been a problem for me for more than a year. Any time I try to update my Forma, within 1 or 2 sync's my database is corrupted and I start getting errors backing up the database and the device stops "remembering" where I was in a book I was reading. I immediately downgrade to 4.35.20400, restore a backup of the database, and life goes on just fine until I try and update again. Once I left the WiFi on and my Forma updated itself to a newer version with the same result.

This problem has persisted with me since Calibre 6 and my old Windows 10 system.

Is there some good way for me to try and diagnose this?

[ownedbycats]

Newer versions of the firmware have issues with database corruption. The general consensus is the best way to prevent it is to reboot the device before connecting.

[rb431]

Originally Posted by ownedbycats

Newer versions of the firmware have issues with database corruption. The general consensus is the best way to prevent it is to reboot the device before connecting.

Ahhhhh, this makes total sense. I have NickelMenu installed now with a reboot menu option and I have upgrade to the latest firmware. So far, so good. Let's see what it's like in the long run.

Thank you for the information.

[threebluestars]

So I use Store reading point, but after updating Calibre and the plugins, it's not saving the 100% in the #koboreadpct column like it used to - the column is blank. When I go to run Store again, it does have the date I finished reading and says 100% in the dialog popup so it's being stored somehow, but I can't see it's finished in my column anymore.

[DNSB]

Originally Posted by threebluestars

So I use Store reading point, but after updating Calibre and the plugins, it's not saving the 100% in the #koboreadpct column like it used to - the column is blank. When I go to run Store again, it does have the date I finished reading and says 100% in the dialog popup so it's being stored somehow, but I can't see it's finished in my column anymore.

Have you double checked your custom column names and types? For instance, koboreadpct's lookup name in the column definition should not have the leading # (that automagically added to the lookup name for custom columns) and the data type is integer.

[chaley]

Originally Posted by threebluestars

So I use Store reading point, but after updating Calibre and the plugins, it's not saving the 100% in the #koboreadpct column like it used to - the column is blank. When I go to run Store again, it does have the date I finished reading and says 100% in the dialog popup so it's being stored somehow, but I can't see it's finished in my column anymore.

Sometimes Kobo Utilities loses how to recognize a device, especially after a hard reset or a format, and sometimes after a firmware upgrade.

To check this, start calibre, plug in your device, start Kobo Utilities, open the "Devices" tab, then ensure that the attached device is being recognized with the device name you expect.


Then open the "Profiles" tab to ensure that the profile you have used to set the columns references the same device you saw above or "*any device". Also make sure that "Store current bookmarks/reading position on connect" is checked.

[threebluestars]

Originally Posted by chaley

Sometimes Kobo Utilities loses how to recognize a device, especially after a hard reset or a format, and sometimes after a firmware upgrade.

To check this, start calibre, plug in your device, start Kobo Utilities, open the "Devices" tab, then ensure that the attached device is being recognized with the device name you expect.
Attachment 208913

Attachment 208914

THANK YOU! It was the devices. Weirdly it didn't like me specifying "Kobo Aura H2O" and wanted it to say "Any Device" - why, I don't know, but it's working under that setting.

[DNSB]

Originally Posted by threebluestars

THANK YOU! It was the devices. Weirdly it didn't like me specifying "Kobo Aura H2O" and wanted it to say "Any Device" - why, I don't know, but it's working under that setting.

At times, I found that specifying a device caused issues when I did factory resets or firmware updates and something changed in how the device was seen. I just use Any device now since that doesn't care what Kobo ereader I connect and I no longer use different profiles for different devices.

[JSWolf]

Originally Posted by DNSB

At times, I found that specifying a device caused issues when I did factory resets or firmware updates and something changed in how the device was seen. I just use Any device now since that doesn't care what Kobo ereader I connect and I no longer use different profiles for different devices.

The reason the device stopped being recognized when doing a reset is because driveinfo.calibre contains the device info. When that gets deleted, the Kobo is no longer recognized as the same device it once was.

[chaley]

Originally Posted by DNSB

At times, I found that specifying a device caused issues when I did factory resets or firmware updates and something changed in how the device was seen. I just use Any device now since that doesn't care what Kobo ereader I connect and I no longer use different profiles for different devices.

I started that way only to discover that my wife and I require individualized reading positions, read status, and backups. Device profiles solve these. I am OK with occasionally needing to "refresh" them.

We have the same problem with collections. Device profiles don't help there so I generate collections with a template. It checkes the device serial number then generates the appropriate collections for the device/person. The device serial number never changes so no "refresh" ever needed.

[JSWolf]

Originally Posted by chaley

I started that way only to discover that my wife and I require individualized reading positions, read status, and backups. Device profiles solve these. I am OK with occasionally needing to "refresh" them.

We have the same problem with collections. Device profiles don't help there so I generate collections with a template. It checkes the device serial number then generates the appropriate collections for the device/person. The device serial number never changes so no "refresh" ever needed.

Can the device settings for Kobo Utilities be changed to use the device serial number as the identifier?