Firmware 4.38.21908

[Aleron Ives]

It's not so weird anymore. For quite some time now, even returning to My Books before you connect over USB is not enough to prevent database corruptions and other wonkiness. Recent firmware doesn't seem to close the database properly when you connect, so you have to reboot the device before you connect now in order to force a database closure.

[Quoth]

Is it a windows thing? I'm not seeing that issue on Linux if I go to Home / My Books first and wait till black update screen is gone after exject before unplugging.
Multiple Kobo ereaders.

[JSWolf]

Originally Posted by Quoth

Is it a windows thing? I'm not seeing that issue on Linux if I go to Home / My Books first and wait till black update screen is gone after exject before unplugging.
Multiple Kobo ereaders.

It is not a Windows thing. I go tot he home screen, plug in my Libra 2, and once ejected, wait until I'm back to the home screen before unplugging the USB cable (if I am done).

[meeera]

Originally Posted by Quoth

Is it a windows thing? I'm not seeing that issue on Linux if I go to Home / My Books first and wait till black update screen is gone after exject before unplugging.
Multiple Kobo ereaders.

I have no idea what it's related to. I connect all the time while in a book without going to Home first, without trouble/corruption. Just did it again tonight to transfer a book. Ejected from Calibre, waited for the reader to realise it was disconnected before unplugging. No issues. I'm on 4.38.21908 on a Libra 2 with a Mac.

[Quoth]

Originally Posted by JSWolf

It is not a Windows thing. I go tot he home screen, plug in my Libra 2, and once ejected, wait until I'm back to the home screen before unplugging the USB cable (if I am done).

But not everyone is on the same version/patches/updates/drivers.

Certainly some people are suffering and some are not. Sufferers write of Explorer vs tray vs Calibre eject. That's Windows.

[ownedbycats]

Ugh, database corrupted again. The first sign was a couple of Kobo Store books that I had to re-download. Then I connected to Calibre and got the message.

Resotred my latest db backup, hope that fixes it.

[JSWolf]

Originally Posted by Quoth

But not everyone is on the same version/patches/updates/drivers.

Certainly some people are suffering and some are not. Sufferers write of Explorer vs tray vs Calibre eject. That's Windows.

Yes, they are on the same version if they are posting in this thread. As for the patches, true that. But I don't know if any of that makes a difference. As for drivers, yes we are all using the same drivers with the same firmware version.

[Quoth]

Originally Posted by JSWolf

Yes, they are on the same version if they are posting in this thread. As for the patches, true that. But I don't know if any of that makes a difference. As for drivers, yes we are all using the same drivers with the same firmware version.

I meant version, drivers and patches of Windows, not the Kobo.

[npr]

No problem here using two Libra 2's with windows 10.
Use Calibre and don't take any special measures to connect / disconnect.
Wonder if it's being caused by a anti virus programme??

[DNSB]

Originally Posted by npr

No problem here using two Libra 2's with windows 10.
Use Calibre and don't take any special measures to connect / disconnect.
Wonder if it's being caused by a anti virus programme??

I find that doubtful. My procedure for triggering the issue is to open any book, read a few pages and then connect to the computer (MacOS Sonoma, Windows 11, SUSE Tumbleweed, etc.). I will see the write ahead log and shared memory files (.sqlite-wal and .sqlite-shm file extensions) which will be removed when the database is closed.

To me, this suggests that it is an issue with the way my Kobo's close the database before the USB connect. My Sage misbehaves the most often while my Clara HD despite having a much larger database file is less likely to exhibit this behaviour.

When I tried reducing the number of books on my Sage to <100, I was unable to generate the failure to close in a test of about 25 connects.

While a database connection is open on a WAL-mode database, SQLite maintains an extra journal file called a "Write Ahead Log" or "WAL File". The name of this file on disk is usually the name of the database file with an extra "-wal" suffix, though different naming rules may apply if SQLite is compiled with SQLITE_ENABLE_8_3_NAMES.

The WAL file exists for as long as any database connection has the database open. Usually, the WAL file is deleted automatically when the last connection to the database closes. However, if the last process to have the database open exits without cleanly shutting down the database connection, or if the SQLITE_FCNTL_PERSIST_WAL file control is used, then the WAL file might be retained on disk after all connections to the database have been closed. The WAL file is part of the persistent state of the database and should be kept with the database if the database is copied or moved. If a database file is separated from its WAL file, then transactions that were previously committed to the database might be lost, or the database file might become corrupted. The only safe way to remove a WAL file is to open the database file using one of the sqlite3_open() interfaces then immediately close the database using sqlite3_close().

[Quoth]

I've about 1,200, 2,000, 3,500 and 6,000 on four different Kobo Sage models and no issues. Linux Mint, Mate, Caja and ejecting from Calibre. Not all on the same Linux Mint.

[geek1011]

If this database issue still persists, I think I can create a NickelHook mod to fix it.

[Artemide]

It could be a windows drivers issue, like an incompatibility between last firmware and Os.
In order to better understand, someone could check if with Kobo uncaged patch problem still appears.

My Kobo Lybra 2 is still on 4.35 version, and remains with it until a serious upgrade will be released.

It's unpleasant that users make brainstorming after pay money for good devices with poor support. Forgive the polemic.

@Quoth, is your calibre full working with Linux distro? On mine Calibre built in reader is missing (Fedora and Manjaro)

[DNSB]

Originally Posted by Artemide

It could be a windows drivers issue, like an incompatibility between last firmware and Os.
In order to better understand, someone could check if with Kobo uncaged patch problem still appears.

I see the issue on MacOS Sonoma, Windows 11 x64 and Suse Tumbleweed. It is not a Windows issue since the Kobo should have closed the database prior to the FAT32 partition being exposed over USB.

[Quoth]

Originally Posted by DNSB

I see the issue on MacOS Sonoma, Windows 11 x64 and Suse Tumbleweed. It is not a Windows issue since the Kobo should have closed the database prior to the FAT32 partition being exposed over USB.

I agree that the database should have been "closed". I will look and see are the "wal" file(s) there when I connect.

Baffling that it's not all devices.
Is it related to Country, SideloadedMode true/false, directly downloaded bought books, sync, sync & having more than one device, WiFi or BT on, how last book was opened, where on GUI you on, how long between plug in USB and tapping Connect or what?

Also the bug of WiFi turning on when you enable BT is still there, and it is a bug as you can turn off the WiFi and BT still works.
Curious Sage tries to first open my newest BT keyboard as Audio first and then fails that (showed in GUI).