View Single Post
Old 03-05-2024, 02:49 PM   #7
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,564
Karma: 169115148
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Lys View Post
That said, your issue seems more connected to database corruption than anything related to the device itself. I haven't had a DB corruption since forever now, but a couple of reasons you may corrupt the DB are:
1) Connecting to Calibre while you have an ebook open on the device (I always make sure to be on the home page before connecting)
2) Reconnect to Calibre before your Kobo has properly digested the new ebooks in its database.
3) The database is not properly closed before the USB connection is finalized. This is easily diagnosed by seeing .sqlite-wal and .sqlite-shm files in the .kobo directory. Kobo is aware of this issue and it should be fixed in the next firmware release though my hopes of that happening Real Soon Now have long been dashed. This seems to happen more often when using the Sage or Elipsa.
DNSB is offline   Reply With Quote