View Single Post
Old 08-10-2023, 12:56 PM   #123
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,929
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Cootey View Post
This works, but I was traumatized by repeated db corruptions and wasted calls to Kobo back when the Elipsa1 was new, so I rebooted just to be safe.
The current 4.37.21586 firmware seems to have DB corruption issues on the Sage. Given the dirty bit errors that Windows comes up with and the number of .wal (write-ahead logging) files that I've seen when connected to my computer, I strongly suspect that the database is not being properly closed before the connection is initiated since the .wal files should be removed when the last connection to a SQLite database is closed.

I'm still rebooting before connecting and likely will until the next firmware version arrives.
DNSB is offline   Reply With Quote