View Single Post
Old 09-25-2024, 06:04 AM   #53
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,943
Karma: 146918083
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by compurandom View Post
That may be so, but continuing to open the database can't possibly make things better, and that's even more true if the linux side on the kobo wasn't actually made read only.

And not checking for this before opening the database makes this very difficult to detect and debug.

If I knew that the database was damaged, rather than let calibre damage it more by using it, I could reboot the kobo, attempt repair on the database before it gets worse, and/or restore the database from backup before it goes for another 2-3 days and gets further corrupted to the point where restoring the database isn't going to help more than just deleting the database and rebuilding it.

Without some kind of detection of this problem, I'm left with the best option of rebooting the kobo before every usb connection.

And no, going back to home screen doesn't fix this issue and never did. I'd say that maybe it makes it less likely, but really I think it's just waving a rubber chicken at the problem.
I went back to the home screen on my Libra 2 and it always worked for me.
JSWolf is offline   Reply With Quote