View Single Post
Old 09-09-2021, 09:20 AM   #45
Cootey
Absentminded Reader
Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.Cootey ought to be getting tired of karma fortunes by now.
 
Cootey's Avatar
 
Posts: 1,345
Karma: 7442365
Join Date: Apr 2017
Device: Kobo Mini, Libra Colour & Elipsa; Kindle Paperwhite 3 & 4; iOS apps
Quote:
Originally Posted by davidfor View Post
With the Kobo desktop, it didn't happen every time. And it didn't happen every time with calibre, but, it was more often. I was also able to reproduce it with DB Browser for SQLite if I updated something.
That’s fascinating that you were able to reproduce the issue with DB Browser. Is this a problem with just the Elipsa, or with all Kobos running the 4.28.x firmware?

Since the database is being left open by the Kobo, would we be able to avoid corruption by power cycling the Kobo before connecting to a computer?

Quote:
Originally Posted by davidfor View Post
It's always a problem reporting problems like this in ways they can understand. I'm not sure how I would. But, I discussed it with one of the people on the beta list and he was able to see what was happening. I expect it will be fixed in the next release, but we will have to wait and see.
I’ll probably give Kobo a call and update one of the cases I had open with them. It couldn’t hurt.


Sent from my iPhone using Tapatalk Pro
Cootey is offline   Reply With Quote