View Single Post
Old 06-25-2024, 09:39 PM   #17
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,377
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Haesslich View Post
Oh hell, I just hash that happen yesterday. My new Libra Colour stopped being able to sync, and I just wiped it to start fresh.

I could've saved myself the effort of they'd released it sooner.
Note that this helps with the issue where the database was not properly closed before the USB connection. One very noticeable symptom was the presence of *.sqlite-wal and *.sqlite-shm (WAL for write-ahead logging and SHM for shared memory) files in the .kobo directory after the connection.

You can still corrupt the database by not safely ejecting, having a flakey USB cable, etc.
DNSB is offline   Reply With Quote