View Single Post
Old 07-05-2024, 03:22 PM   #11
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,784
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by ownedbycats View Post
By that logic, we should also move this thread and this one. After all, it only matters for Kindle books.
The difference being is that the Kobo database corruption issue has nothing to do with calibre since simply connecting your Kobo to a computer over USB could trigger the issue while the two threads you mention are connected to calibre importing Kindle format ebooks.

BTW, the latest 4.38.23038 firmware ( 4.39.23027 for the Libra Colour, Clara Colour and Clara BW ) do close the database before a USB connect so that source of database corruption has been fixed. It's still possible to corrupt that database by not safely ejecting, etc. but the major cause is no longer with us.
DNSB is offline   Reply With Quote