Thread: [Closed] Issues with Version 6
View Single Post
Old 07-11-2022, 10:58 PM   #74
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 merniegirl View Post
Had the same problem as sDs910 after v6 install on iMac running Big Sur Calibre couldn't access or install any books I has stored or purchased today after installing it yesterday. Kept getting this message: CorruptError: database disk image is malformed
Traceback (most recent call last):
File "calibre/gui2/device.py", line 87, in run
File "calibre/gui2/device.py", line 548, in _books
File "claibre/devices/kobo/driver.py", line 2008, in books
apsw.CorruptError: CorruptError: database disk image is malformed
Correction required rolling back my stored Calibre library to yesterday in Time Machine, a hard reset of Kobo Clara and dumping v6 for v5.4
Wow, that was bad timing. The corrupt database error has nothing to do with calibre. The database was already broken when calibre looked at it. If you update calibre again, it will be OK. If you want to be safe, connect the device without calibre running and take a copy of the database. This is in the ".kobo" directory and is named "KoboReader.sqlite". If you then run calibre and have a problem, you can restore the database before ejecting the device.

But, if you do have a problem, you should check the database copy to make sure it wasn't already corrupted.
davidfor is offline