View Single Post
Old 08-11-2017, 09:07 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Blaise View Post
I succesfully loaded books from calibre to my Kobo (many times).
But since 6 month about, when I try to delete a book from my Kobo with calibre I got a error message saying: "problem of communication with your device" and I get these information(see below) - What should I do ?


calibre, version 3.6.0
ERREUR : Erreur: Erreur pendant la communication avec le périphérique

CorruptError: database disk image is malformed

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 88, in run
File "site-packages\calibre\gui2\device.py", line 616, in _delete_books
File "site-packages\calibre\devices\kobo\driver.py", line 509, in delete_books
File "site-packages\calibre\devices\kobo\driver.py", line 2150, in delete_via_sql
File "site-packages\calibre\devices\kobo\driver.py", line 453, in delete_via_sql
File "c:\t\t\apsw-9hooel\apsw-3.13.0-r1\src\cursor.c", line 236, in resetcursor
CorruptError: CorruptError: database disk image is malformed
Looking at where the error occurred in the driver, I'm surprised you didn't get an error when calibre was getting the book list from the device. That could mean the corrupted part of the database is an index. And compressing the database might fix it. My Kobo Utilities plugin has a function to do this. I'm not certain it will work, but you will be in no worse position than you currently are.

If this doesn't work, then JSWolf's and PeterT's suggestions are the way to recover.
davidfor is offline   Reply With Quote