Firmware 4.38.21908

[DNSB]

Originally Posted by JSWolf

Have you read any KePub between connecting tot he computer when you've seen that the database remains open? I don't have this problem and I also have not read any KePub with this firmware.

It doesn't matter if I read epub or kepub in my testing.

[Aleron Ives]

Originally Posted by Quoth

I wonder is it kepub usage (even if not the last ebook) that causes it?

I only read KEPUB and have never had the problem.

[DNSB]

Originally Posted by Amon_Re

Can confirm it also happens with Calibre & Fedora Linux, it's not limited to windows and must be something on the Kobo itself that f's up.

Given that the failure to close the database which would flush the .sqlite-wal and .sqlite-shm files must occur before the USB connection, you are correct that it is an issue on the Kobo. In my testing, it happened on MacOS Sonoma, Windows 11 x64 and SUSE Tumbleweed.

I have also found that forcing a reboot before connecting to the computer keeps the issue from showing up for me.

[compurandom]

Originally Posted by meeera

This isn't necessarily dispositive, but I read mostly kepubs and haven't had this issue. They're sideloaded kepubs though, not Kobo-bought-and-synced books.

I also read almost exclusively kepubs. Both sideloaded and otherwise.

Sometimes I have issues, sometimes I don't.

There may be a relationship between when a kepub is closed and either time or activities after it is closed.that allows the database to close without a reboot.

[Aleron Ives]

I always tap "Back to My Books" from the reading menu and then connect the cable a few seconds later.

[Number9]

Originally Posted by Aleron Ives

I only read KEPUB and have never had the problem.

Same here!

[stangri]

So is this update safe to install? Has anyone noticed any issues on Libra 2?

[ownedbycats]

There's a slight risk of database corruption that can happen if you connect to the computer, due to the Kobo failing to close the database before exporting to USB. There's three main ways to reduce (hopefully prevent) this:

1. If you use Calibre, use the Kobo Utilities plugin to make a daily backup of the database. You should be doing this anyways. This way, even if it does break, you can restore the most recent backup.

2. Connect only from the home screen. Close any books, especially kepubs.

3. Reboot before connecting. This is overkill for most times, I only do it after importing new books to make sure the database isn't left open.

[JSWolf]

Originally Posted by stangri

So is this update safe to install? Has anyone noticed any issues on Libra 2?

No issues. Just make sure you go to the home screen before plugging the Libra 2 into the computer.

[JSWolf]

Originally Posted by ownedbycats

There's a slight risk of database corruption that can happen if you connect to the computer, due to the Kobo failing to close the database before exporting to USB. There's three main ways to reduce (hopefully prevent) this:

1. If you use Calibre, use the Kobo Utilities plugin to make a daily backup of the database. You should be doing this anyways. This way, even if it does break, you can restore the most recent backup.

2. Connect only from the home screen. Close any books, especially kepubs.

3. Reboot before connecting. This is overkill for most times, I only do it after importing new books to make sure the database isn't left open.

I have no need to reboot. I agree that's overkill and I don't think it's needed.

[ownedbycats]

Originally Posted by JSWolf

I have no need to reboot. I agree that's overkill and I don't think it's needed.

The database may be left open by the import process. Rebooting is the guaranteed method of closing it.

[DNSB]

Originally Posted by JSWolf

I have no need to reboot. I agree that's overkill and I don't think it's needed.

Originally Posted by ownedbycats

The database may be left open by the import process. Rebooting is the guaranteed method of closing it.

In my testing on a Sage, the database is not left open after importing books (telnet and look for the .sqlite-wal and .sqlite-shm extensions). It does get left open after reading a book but not 100% of the time. The reboot takes seconds and saves me from having to restore the database.

As for Jon? Once again he is extrapolating his personal experience on one device to being a universal truth. Stating that other people can't be having issues because it doesn't happen to you is about as inane an attitude as suggesting that since you don't have gout, so no one can be suffering from gout.

[ownedbycats]

Originally Posted by DNSB

In my testing on a Sage, the database is not left open after importing books (telnet and look for the .sqlite-wal and .sqlite-shm extensions). It does get left open after reading a book but not 100% of the time. The reboot takes seconds and saves me from having to restore the database.

Interesting. I did get corruption by immediately re-connecting after an import, I hadn't opened any books though. Do you see anything when syncing to server? I noticed that importing will trigger a new sync.

[DNSB]

Originally Posted by ownedbycats

Interesting. I did get corruption by immediately re-connecting after an import, I hadn't opened any books though. Do you see anything when syncing to server? I noticed that importing will trigger a new sync.

Syncing to the server seems to close the database in my limited testing. Basically, I reboot since it's faster than a manual sync on my Sage.

[Quoth]

I've noticed that straight after import (black screen closed), there is a variable delay before a flash of the Home/My Books screen. The new books are not immediately listed if it's showing "unread" or "all".

So if I'm updating collections or something needing a reconnection I wait till that flash before reconnecting the cable. I don't disconnect the cable after eject (desktop or Calibre on Linux) till I see the black importing screen.