[GUI Plugin] Kobo Utilities

[ownedbycats]

I tried replicating with another book, definitely matched








It didn't replicate this time! maybe I missed a step

[Majutsushi]

Changes in this release:

• Added feature to restore a previously created backup to a device.
• Always include the database in the backup ZIP for simplicity, space savings, and easier restore.
• Set a default backup location so that forgetting to specify a directory doesn't cause the backup feature to silently not do anything.
• Updated fonts in the "Set reader font" feature to firmware 4.39.22801.
• Fixed some translations not loading correctly in some cases.
• Clarified annotations menu entries a bit.

[Phil_C]

Awesome! Thank you for your continued work on this important plugin.

[jillmess]

EDIT - Problem seems to be in my setup. Hopefully sourcing files from a different Kobo device will solve my issue.

I have 3 devices set up in kobo utilities with "Configure options for each device" selected. "Backup the device database on each connection" is selected for 2 of these but not for the third.

The latest version is attempting to backup the database of this third device. Rolling back to the previous version fixes the issue.

Further investigation & info. The "device" in question is one I select when connecting to a folder for transferring books to dropbox. With the latest version it doesn't matter what device I choose when doing this - Kobo Utilities is trying to backup the database even when it is a device that isn't setup in the plugin. This is probably because the device files I have copied to my dropbox folder for this transfer/kepub conversion to work are from my Libra2.

It seems that the latest version is finding these files, associating them with my Libra2 and thus trying to do a database backup. Deselecting the database backup for my Libra2 solves the problem for now.

I assume if I source the device files necessary for the dropbox folder transfer from a different kobo device this will get around the issue?

[Majutsushi]

The plugin identifies devices by their serial number, which on the device is stored in the file ".kobo/version". So if you copy the contents of a mounted device to a folder and connect to it it will appear to the plugin as the same device. If you want the folder to appear as a different device you can just edit that file with a text editor, the serial number is the value at the start of the file, before the first comma.

Nothing should have changed regarding this in the new plugin version, so if it is still happening for you after investigating your setup it would be useful to see a debug log where the device gets connected.

[paulfiera]

I've just started getting this error when plugging my Kobo Aura ONE.

===================================
Falied: Backing up Kobo device database

[Errno 2] No such file or directory: 'E:\\.kobo\\affiliate.conf'

Traceback (most recent call last):
File "calibre\gui2\device.py", line 110, in run
File "calibre_plugins.koboutilities.features.backup ", line 177, in device_database_backup_job
File "shutil.py", line 313, in copyfile
FileNotFoundError: [Errno 2] No such file or directory: 'E:\\.kobo\\affiliate.conf'
===================================

This is with the automatic backup when plugging the device. Manual backup, no problem.

The file 'affiliate.conf' doesn't exist in the .kobo directory.

[DNSB]

Originally Posted by paulfiera

I've just started getting this error when plugging my Kobo Aura ONE.

===================================
Falied: Backing up Kobo device database

[Errno 2] No such file or directory: 'E:\\.kobo\\affiliate.conf'

The file 'affiliate.conf' doesn't exist in the .kobo directory.

That sound as if you deleted the affiliate.conf file. You can copy it from an older backup or, if that backup does not exist, recreate it easily enough:

[General]
affiliate=Kobo

Replace the Kobo with whatever your affiliate is or just leave it for most people. Please use a Unix friendly editor so the EOL is a LF not the CRLF beloved of Windows.

[jillmess]

Originally Posted by Majutsushi

The plugin identifies devices by their serial number, which on the device is stored in the file ".kobo/version". So if you copy the contents of a mounted device to a folder and connect to it it will appear to the plugin as the same device. If you want the folder to appear as a different device you can just edit that file with a text editor, the serial number is the value at the start of the file, before the first comma.

Nothing should have changed regarding this in the new plugin version, so if it is still happening for you after investigating your setup it would be useful to see a debug log where the device gets connected.

Thank you. I have copied files from a different kobo and have also tried just editing the .kobo/version file. Either option worked.

I think this 'folder device' was being backed up previously without me realising. It was only when the updated plugin version started throwing errors because of missing files (I only have the version and sqlite files copied) that it became obvious.

[Majutsushi]

Changes in this release:

• Fixed the backup process failing when some files were not present on the device.

[paulfiera]

Originally Posted by Majutsushi

Changes in this release:

• Fixed the backup process failing when some files were not present on the device.

Thanks!!!

This fixed the missing 'affiliate.conf' file issue.

[paulfiera]

Originally Posted by DNSB

That sound as if you deleted the affiliate.conf file. You can copy it from an older backup or, if that backup does not exist, recreate it easily enough:

[General]
affiliate=Kobo

Replace the Kobo with whatever your affiliate is or just leave it for most people. Please use a Unix friendly editor so the EOL is a LF not the CRLF beloved of Windows.

Thanks.

I have not deleted this file. At least not on purpose.

Majutsushi's latest release solved the problem.

[DNSB]

Originally Posted by paulfiera

Thanks.

I have not deleted this file. At least not on purpose.

Majutsushi's latest release solved the problem.

The latest release does not actually fix the problem of the file being missing. It does prevent the backup process from failing if an expected file is missing.

[Majutsushi]

Note that the backup process had always ignored missing files, that behaviour just got lost in the recent release after some refactoring, and the fix release restored it. So it's possible that some devices were always missing the affiliate file without anyone noticing.

[paulfiera]

Originally Posted by DNSB

The latest release does not actually fix the problem of the file being missing. It does prevent the backup process from failing if an expected file is missing.

That's what I meant. Prevent the backup from failing

I think the missing file has to do with this line in Kobo eReader.conf.

SideloadedMode=true

When signing in the device, SideloadedMode is set to false and affiliate.conf is generated.

[Phil_C]

Originally Posted by paulfiera

I think the missing file has to do with this line in Kobo eReader.conf.

SideloadedMode=true

When signing in the device, SideloadedMode is set to false and affiliate.conf is generated.

That appears to be correct.

My Clara 2E and Clara BW have affiliate.conf. My old Clara HD, which is the only one in SideloadedMode, does not have that file.