[GUI Plugin] Kobo Utilities

[ownedbycats]

Originally Posted by JSWolf

Do you know if it happens on 4.38.23171?

I did a bunch of testing and wasn't able to get it to trigger (even with a kepub open, which reliably triggered it in the bugged versions).

[compurandom]

Originally Posted by ownedbycats

I did a bunch of testing and wasn't able to get it to trigger (even with a kepub open, which reliably triggered it in the bugged versions).

I think there's more than one thing that triggers it and they've fixed some of them.

I think background jobs like rendering covers, and syncing also can trigger it.
It doesn't help that it works for a while after the corruption so I don't notice immediately.
I wonder if it would be possible to add code to the kobo driver to detect this -- or maybe there is some there already?

But I haven't felt like testing since the latest firmware update. It's such a bother to reload everything. Maybe this weekend.

[ownedbycats]

On the bugged versions, I was able to rarely trigger it by re-connecting immediately after importing new books, which made me suspect either the import process or cover generation. But I think DNSB or someone else said that the sql-wal files didn't show up for those processes so I'm not sure.

[JSWolf]

Originally Posted by ownedbycats

On the bugged versions, I was able to rarely trigger it by re-connecting immediately after importing new books, which made me suspect either the import process or cover generation. But I think DNSB or someone else said that the sql-wal files didn't show up for those processes so I'm not sure.

It can't be cover generation as the Kobo driver adds the cover when you send via calibre.

[ownedbycats]

Originally Posted by JSWolf

It can't be cover generation as the Kobo driver adds the cover when you send via calibre.

I don't think it's 100% reliable— occasionally I can see a newly-imported sideload switch from the generic text to the embedded cover. I'm not sure why it happens though.

[compurandom]

Originally Posted by ownedbycats

On the bugged versions, I was able to rarely trigger it by re-connecting immediately after importing new books, which made me suspect either the import process or cover generation. But I think DNSB or someone else said that the sql-wal files didn't show up for those processes so I'm not sure.

Even if cover generation doesn't leave the database open, you could still get filesystem corruption that messed with the database. That would be much much harder, however. But that could explain why it is hard to reproduce too.

Does calibre always send a cover, or just when it has one?

Also, I'm not saying cover generation specifically causes it, I'm just saying things like that might.

[orchidreader]

Originally Posted by DNSB

Do you get any message about database corruption? In KU, what does Check database under the Database items report?

Also are you using Nickel or an alternative reader (KOReader, Plato)?

Sorry, was busy this week. I did check the database using KU and it just says OK. Whenever I use the Restore current bookmark, my book just disappears. It says it's in the Main Device memory but Kobo doesn't display the book. I can still see the kepub in the kobo memory when I plug it to Windows. It's really annoying but the only workaround so far that I'm doing is to factory reset my Kobo everytime I have to update the reading progress and capture last reading location to Calibre.

[orchidreader]

Originally Posted by orchidreader

Sorry, was busy this week. I did check the database using KU and it just says OK. Whenever I use the Restore current bookmark, my book just disappears. It says it's in the Main Device memory but Kobo doesn't display the book. I can still see the kepub in the kobo memory when I plug it to Windows. It's really annoying but the only workaround so far that I'm doing is to factory reset my Kobo everytime I have to update the reading progress and capture last reading location to Calibre.

Thanks for everyone's insight, I finally fixed my issue.

I was testing a few things when I thought I should just force the update for the reading % in my Kobo. So I connected my device and edited metadata.calibre and I looked for the book I'm reading, changed the value to what I need and saved. Expectedly, this corrupted my device database so I tried to factory reset, repair, and signing out from my account but none of it worked, my database is still corrupted/malformed even after resetting. So I decided to just format my device through Windows. After reformatting the device, everything went fine. The reading info is now showing up correctly, using the Restore function of KU no longer sends my books to the void.

Not sure what happened but it seems that my device internal database/memory (not sure if this even exists) was corrupted and it's not updating no matter what I do. The reformat reset that database and I'm finally happy that I can use my Calibre Library correctly.