View Single Post
Old 08-23-2014, 12:15 AM   #4
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,329
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by PeterT View Post
Is it just me, or are others also seeing more instances of database corruption with F/W 3.5.0. Implicit in this statement is of course, this only applies to those using NICKEL to read material, and not CoolReader or KOReader.
Not sure. I had an instance where a book was showing as having no path running Calibre in debug mode but then my Aura HD crashed to a factory reset and after the rebuild, everything was okay again.

What I have noticed is that deleting books from Calibre (1.206) is again not a good idea. I forgot to delete a book and/or it's annotations before connecting to my computer. After deleting the book from Calibre and replacing it, I got that lovely problem where any attempt to change pages crashed back to the home page with the book marked as finished and a stack.log file generated. Home page showed 2 annotations while trying to open annotations says no annotations. Deleted the book from the Kobo GUI, reloaded it and no issues noticed.

And no "I'm not sure either way" item to vote for in the poll.

Regards,
David

Last edited by DNSB; 08-23-2014 at 12:39 PM.
DNSB is offline   Reply With Quote