[GUI Plugin] Kobo Utilities

[ownedbycats]

Feature request: Would it be much effort to add a "don't update existing font settings" checkbox to the set reader font? I like to set a default one in advance as it prevents mishaps such as giant font size being carried over from another book (always a bit amusing when that happens). But there's no way to tell which books are missing one.

Also, is it intended that "Update metadata -> date added" doesn't work on Kobo store books?

[Bembo]

Hi, is this the right thread to post for issues with Kobo Utilities? I have been able to use it to backup my device database on Kobo Clara HD but recently I get an error saying that it failed to create a backup. This is the error:

Result of running 'PRAGMA integrity_check' on database on the Kobo device:   
*** in database main 
*** On tree page 67266 cell 0: invalid page number 218103808 
On tree page 66937 cell 0: invalid page number 218310400 
On tree page 67533 cell 52: 2nd reference to page 67265 
On tree page 47550 cell 102: 2nd reference to page 66998 
Page 66269 is never used 
Page 66936 is never used

And also this error on connecting the device:

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

CorruptError: database disk image is malformed

Traceback (most recent call last):
  File "calibre\gui2\device.py", line 87, in run
  File "calibre_plugins.koboutilities.jobs", line 197, in do_device_database_backup
  File "calibre_plugins.koboutilities.action", line 6095, in check_device_database
apsw.CorruptError: CorruptError: database disk image is malformed

I also had a weird battery error recently where it seemed like the battery was depleting really quickly, but a restart fixed that I think. Not sure if related. Otherwise, I've been able to read and use it just fine.

Any advice would be much appreciated! (Sorry if there is a better place to post this, but since it relates to KU I figured I might try here.)

[ownedbycats]

Your database is corrupted.

You might be able to fix it by running the 'compress database' option.

If not, you have backups enabled, so restore the last working one by unzipping to your .kobo folder, ejecting, and rebooting the device.

[Bembo]

Originally Posted by ownedbycats

Your database is corrupted.

You might be able to fix it by running the 'compress database' option.

If not, you have backups enabled, so restore the last working one by unzipping to your .kobo folder, ejecting, and rebooting the device.

Thank you. I had previously had to restore from one of my archived backups a few weeks ago, and it worked fine for at least a week... which is why I didn't expect it to be corrupted again. I did it again and it seems fine now. Is there any way to restore my annotations from the more recent backup? It seems that they were marked as 'corrupt' so they aren't standard .zip files anymore.

[davidfor]

Originally Posted by Bembo

Thank you. I had previously had to restore from one of my archived backups a few weeks ago, and it worked fine for at least a week... which is why I didn't expect it to be corrupted again. I did it again and it seems fine now. Is there any way to restore my annotations from the more recent backup? It seems that they were marked as 'corrupt' so they aren't standard .zip files anymore.

Yes and no. It will depend on exactly what is wrong with the database. If it is badly corrupt, there will be no way to open it and read the data. If it can be opened, you can try and export the contents of the "Bookmarks" table and import it into the working database.

[ownedbycats]

It's not a huge priority, but I did something in Kobo Utilities that resulted in all the unread books in my 'to be read' collection appearing in alphabetical order. But now I've finished some books and added other ones they're jumbled up again and can't remember how to put them in alphabetical order again. Any ideas?

[davidfor]

Originally Posted by ownedbycats

It's not a huge priority, but I did something in Kobo Utilities that resulted in all the unread books in my 'to be read' collection appearing in alphabetical order. But now I've finished some books and added other ones they're jumbled up again and can't remember how to put them in alphabetical order again. Any ideas?

Collection can be sorted on the device. But, I don't remember if that is remembered for each collection.

The plugin has the function "Order Series Shelves" which can be used to order any collection, but, it doesn't have an option for alphabetical. And, I don't think it actually has an effect in recent firmware.

[compurandom]

Originally Posted by davidfor

Collection can be sorted on the device. But, I don't remember if that is remembered for each collection.

On the kobo, it is. I use this all the time. Collection sort order (and filters) is separate for each collection, and separate for each series, and separate for the all books screen, etc.

Also, the sort orders and filters are saved in the config file that the Kobo extended plugin backs up.

[ownedbycats]

I think I remember how I did it: I temporarily set an arbitrary #lastread that was the same for all the books, restored that to device, and then cleared it in my Calibre library.

[Uncle Robin]

I just ran the database check in Kobo Utilities - is this something to be concerned about?

Result of running 'PRAGMA integrity_check' on database on the Kobo device:


*** in database main ***
Main freelist: size is 5030 but should be 5031

[ownedbycats]

If I remember right, freelist is just the bits of the database that isn't in use anymore but hasn't been cleaned up yet with a vacuum. Somehow the database lost count of that. Compacting the database ought to fix it.

[enuddleyarbl]

Over on the Kobo forum in the latest firmware thread, you (davidfor) mentioned you were thinking of adding a backup of BookReader.sqlite to (I assume) Kobo Utilities:

https://www.mobileread.com/forums/sh...344604&page=40

I'm wondering if you could test for a bad BookReader.sqlite file by watching its file size. In the one case where I noted it, the size of that file went from 15KB to 45MB when it went bad. That "bad" size was very close to the size of KoboReader.sqlite. Maybe a comparison to that would work?

Also, is there any way Kobo Utilities could be involved with the size change in BookReader.sqlite (maybe a typo)? It just seems odd that the "bad" size would be so close to the size of KoboReader.sqlite. I'm not saying it's so, I'm just wondering.

[DNSB]

Originally Posted by DaveLessnau

I'm wondering if you could test for a bad BookReader.sqlite file by watching its file size. In the one case where I noted it, the size of that file went from 15KB to 45MB when it went bad. That "bad" size was very close to the size of KoboReader.sqlite. Maybe a comparison to that would work?

Also, is there any way Kobo Utilities could be involved with the size change in BookReader.sqlite (maybe a typo)? It just seems odd that the "bad" size would be so close to the size of KoboReader.sqlite. I'm not saying it's so, I'm just wondering.

As far as I can tell from checking the KoboUtilities source, there are no references to BookReader.sqlite present.

Looking at my Sage and Clara HD, I've seen BookReader.sqlite balloon on a couple of occasions but it has always returned to it's smaller size (~875kb) while the KoboReader.sqlite has hung around 51MB on the Sage and 860MB on the Clara HD.

[enuddleyarbl]

Originally Posted by DNSB

As far as I can tell from checking the KoboUtilities source, there are no references to BookReader.sqlite present.

Looking at my Sage and Clara HD, I've seen BookReader.sqlite balloon on a couple of occasions but it has always returned to it's smaller size (~875kb) while the KoboReader.sqlite has hung around 51MB on the Sage and 860MB on the Clara HD.

Thanks for looking into that. I really didn't think Kobo Utilities (or anything on our non-Rakuten side of things) could have anything to do with the BookReader.sqlite file. But, the similarity in sizes when bad made me wonder.

[davidfor]

Originally Posted by DaveLessnau

Over on the Kobo forum in the latest firmware thread, you (davidfor) mentioned you were thinking of adding a backup of BookReader.sqlite to (I assume) Kobo Utilities:

https://www.mobileread.com/forums/sh...344604&page=40

I'm wondering if you could test for a bad BookReader.sqlite file by watching its file size. In the one case where I noted it, the size of that file went from 15KB to 45MB when it went bad. That "bad" size was very close to the size of KoboReader.sqlite. Maybe a comparison to that would work?

Also, is there any way Kobo Utilities could be involved with the size change in BookReader.sqlite (maybe a typo)? It just seems odd that the "bad" size would be so close to the size of KoboReader.sqlite. I'm not saying it's so, I'm just wondering.

I will probably add backing up the BookReader.sqlite file, but, I am not planning to add any checks for it. I think the size rule is to simple. How big it is supposed to be depends on how much it is used. For people borrowing a lot of library books, or with a Kobo Plus subscription, it is possible it should be much larger.