2.6.2 No longer processing Calibre created Kepubs

[jgoguen]

I believe it's only side-loaded KePubs.

[jackastor]

Originally Posted by jgoguen

I believe it's only side-loaded KePubs.

It is only side loaded Calibre/user created kepubs.

regards

Jack

[6charlong]

Thank you both for your help. If I understand, I should be okay to use Wi-Fi to download KePub books from Kobo.

My problem is that I have over 1,000 books I've bought over the past 9 years and I like to reread many of them. Of course, most of them are plain vanilla ePubs. But to me, the wonderful way Kobo eReader's presents books is what makes them special, so I'll probably still have to wait for this glitch to be fixed before I download directly over Wi-Fi.

As long as I don't get that update on my present KeReaders I can still download the ePub version of their books and convert them to KePub manually.

[paola]

I just tried this out, and I got an error actually:

calibre, version 1.6.0
ERROR: Error: Error communicating with device

database disk image is malformed

Traceback (most recent call last):
  File "site-packages\calibre\gui2\device.py", line 85, in run
  File "site-packages\calibre\gui2\device.py", line 510, in _sync_booklists
  File "calibre_plugins.kobotouch_extended.device.driver", line 289, in sync_booklists
  File "calibre_plugins.kobotouch_extended.device.driver", line 285, in __rows_needing_imageid
DatabaseError: database disk image is malformed

HOWEVER, the book is there, as a kepub.epub, and I can read it without problems!

[jgoguen]

A malformed database and it still works? Cool!

Looks like it just wouldn't have updated the image IDs in the database. Where that error came from is where I look for books without an image ID and give them what I think is tre correct image ID.

[jackastor]

Actually I should point out its not an issue with books that were on there before the 2.6.2 update its all new sideloaded caliber created kepubs

[paola]

Originally Posted by jackastor

Actually I should point out its not an issue with books that were on there before the 2.6.2 update its all new sideloaded caliber created kepubs

jackastor, yes the one I transferred was a new book I was sending as sideloaded kepub, just to try. However I had just updated to Calibre 1.6, don't know whether that matters as well. I am on a Mini on firmware 2.6.2. I connected it again later to my computer, and got no issues. (well, there is one issue where windows asks me to fix the errors on the device, but I simply ignore it).

[PeterT]

FYI: I just updated my Wife's mini to 2.6.2 and using calibre 1.6.0 and the current version of Kobo Extended Driver had no problems sending a book in kepub format to the Glo.

However there are a few weird things

• I'm accustomed to seeing newly added material show up on the Mini's home screen; not the case here.
• Even after reading a bit of the book, it is not on the home screen.

AH... the time was not set correctly on the Mini!

Not sure whether this was an artifact of the upgrade OR her Mini (which is rarely used) jsut not being set to the correct time.

Now the book IS on the home page.

Now to try adding another book and see what happens

Success; book added AND on Front Screen.

So sorry to say, there does NOT seem to be an issue with 2.6.2 and sideloaded kEpubs.

[paola]

Originally Posted by PeterT

So sorry to say, there does NOT seem to be an issue with 2.6.2 and sideloaded kEpubs.

so it looks like updating Calibre to 1.6.1 will solve the issue for those who have it on previous Calibre versions!

[jgoguen]

I'd be very surprised. The calibre version has very little to do with the process, except for making sure you have the minimum version to install he plugin.

[PeterT]

Originally Posted by paola

so it looks like updating Calibre to 1.6.1 will solve the issue for those who have it on previous Calibre versions!

I will install an older portable version and try, but I seriously doubt there ever was an issue.

**UPDATE**

I have installed both Calibre Portable 1.4.0 and Calibre Portable 1.5.0; added a single book to each of the new portable libraries, installed the KoboTouchExtended driver, disabled both the Kobo Reader Device Interface and the Kobo Touch drivers, and finally sent the book added to the Mini.

No issues with either 1.4.0 or 1.5.0.

I could continue but seeing these builds were from September 20th and September 29th respectively, and the issue was initially reported on October 6th, I think this was a total non-issue from the get go.

As I said earlier, I did notice that the Mini had an incorrect time set after the update; I don't know if it was correct before hand, but I tend to wonder if the initial problem was caused by a faulty time stamp.

[jackastor]

Originally Posted by paola

jackastor, yes the one I transferred was a new book I was sending as sideloaded kepub, just to try. However I had just updated to Calibre 1.6, don't know whether that matters as well. I am on a Mini on firmware 2.6.2. I connected it again later to my computer, and got no issues. (well, there is one issue where windows asks me to fix the errors on the device, but I simply ignore it).

Hmm I see that error with Windows all the time with a properly ejected reader too. Always there is no error when scanned and it slows things so much down.

regards

JAck