Thread: Libra 2 and Calibre - all sorts of strange behaviour
View Single Post
Old 03-13-2022, 07:45 PM   #10
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 JSWolf View Post
Are you running firmware version 4.31? If so, then that's the reason for these errors and the database corruption. There are two solutions.

1. Install firmware 4.30 and install the patch to not update the firmware via WiFi

2. Install firmware 4.30 and do not sync. Keep WiFi off.

The problem is that 4.31 is rather buggy and is known to corrupt the database. I suggest you read the thread on the 4.31 firmware.

Firmware 4.31.19086
Jon: Please stop answering any question about anything. @w00dent0p is having a problem with sending a book to the device using the KoboTouchExtended driver. It is clear from the error message where this is happening. It is COMPLETELY and UTTERLY unrelated to the firmware running on the device. And if you would bother to actually read the post, you would see this. Or at least you would see that you have absolutely no idea about what is going on and would hence not make a completely and utterly useless reply to the post. I don't know about others here, but you useless responses are pissing me off.

Edit:
And yes, I should read the full message as I was only concerned with the failure in the transformation of the book to the kepub. The database problem is separate and I stand by the idea that your basic type of response. And honestly, not even commenting on the first error demonstrates thos.


@w00dent0p: Did you get the first error when you tried sending the book again? That is related to the book and possibly how the extended driver is coded.
Last edited by davidfor; 03-13-2022 at 07:55 PM.
davidfor is offline   Reply With Quote