![]() ![]() ![]() And it doesn't write to the database except when you manually start one of the functions that do updates. ![]() If the Kobo Utilities plugin is causing a problem, it happened when you last connected the device. And it is probably happening when the database on the device is first accessed. That error is happening while the driver is trying to get the list of books from the device. If you are still seeing the above error, then it is has nothing to do with Kobo Utilities plugin. I think when this plugins try to read or write the reading status of ebbok, something is wrong. I ask the KoboUtilities plugin to synchronise reading status and the i have the error. I have then copy my ebooks from calibre to the Kobo and everything is working. ![]() I have hard reset my Kobo (no more kmon, no more nickelmenu, no more ebook). I believe that something else is causing the problem, and calibre just happens to be the only thing that explicitly shows an error about it. But, I do not believe it is a problem caused by calibre. I have posted some suggestions that might help to track down when it happens, but, at the moment, we don't know. There is discussion on it in the Kobo forum. As said, it seems to be an issue with the Elipsa, or the firmware on it. I have no issues with my Forma.ĮRROR: Error: Error communicating with deviceĬorruptError: database disk image is malformedįile "calibre\gui2\device.py", line 89, in runįile "calibre\gui2\device.py", line 515, in _booksįile "calibre\devices\kobo\driver.py", line 1974, in booksĪpsw.CorruptError: CorruptError: database disk image is malformed Most likely a problem with Ellipsa firmware. I am still seeing the problem on Calibre 5.23 and Ellipsa firmware 5. I have tried hard reset, log out/in, and adding books incrementally (instead of all at once). I am seeing the same recurring problem on the Ellipsa. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |