MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader
Reload this Page Aura Aura ONE no longer connects at Calibre launch

Notices

Reply
 
Thread Tools Search this Thread
Old 11-26-2016, 11:39 AM   #1
MauriceH
Junior Member
MauriceH began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2016
Device: Kobo Glo
Aura ONE no longer connects at Calibre launch
My Kobo Aura ONE recently updated its software to version:
4.1.7729 dated 10/10/16

When I plugged my Kobo into my Windows10 PC, I received this error:

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

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 506, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1792, in books
File "c:\cygwin64\home\kovid\sw\build\apsw-3.8.2-r1\src\cursor.c", line 231, in resetcursor
CorruptError: CorruptError: database disk image is malformed

I exited Calibre, downloaded and installed the latest version 2.73
After reading the forums a bit I updated / installed current plugins for Kobo

I still see no books on my device when I look at it from Calibre.
On the device itself I see my previously loaded books.
Also, when I look at the device directory from my PC everything seems to be there.


I still get this error when I plug in my Kobo to the USB and run Calibre.
Also, I have some books on my Kobo that I was reading. When I try to read them now I get an error about Adobe Digital Rights (DRM)

This did not present a problem before the updates.

On Calibre when I go to Device-> Update cached Metadata on device, if get this error:
calibre, version 2.73.0
ERROR: Error: Error communicating with device

'list' object has no attribute 'set_debugging_title'

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 88, in run
File "site-packages\calibre\gui2\device.py", line 536, in _sync_booklists
File "site-packages\calibre\devices\kobo\driver.py", line 935, in sync_booklists
File "site-packages\calibre\devices\kobo\driver.py", line 2236, in update_device_database_collections
AttributeError: 'list' object has no attribute 'set_debugging_title'
Last edited by MauriceH; 11-26-2016 at 12:32 PM.
MauriceH is offline   Reply With Quote
Old 11-26-2016, 12:38 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 45,321
Karma: 168808723
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by MauriceH View Post
My Kobo Aura ONE recently updated its software to version:
4.1.7729 dated 10/10/16

When I plugged my Kobo into my Windows10 PC, I received this error:

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

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 506, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1792, in books
File "c:\cygwin64\home\kovid\sw\build\apsw-3.8.2-r1\src\cursor.c", line 231, in resetcursor
CorruptError: CorruptError: database disk image is malformed
That error message is a pretty good indication that your database is corrupted. The easiest way to fix it is to log out of your KA1 and then sign in to create a new database.

This will remove any annotations, etc. so you might want to grab a copy of the corrupted database before doing the sign out. Depending on how damaged the database is, you may be able to recover some information from it.
DNSB is offline   Reply With Quote
Advert
Old 11-26-2016, 02:16 PM   #3
MauriceH
Junior Member
MauriceH began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2016
Device: Kobo Glo
Problem Solved - NEW Extended Driver WORKS!
After lots of reading on the forums I downloaded and installed the Kobo Extended driver, disabled the other Kobo driver.
After rebooting my Kobo it seemed mostly wiped and prompted me to register again for my Kobo account.
After that, when I rebooted it saw my previously installed books! Plus a couple I had tried to install today!
Looking very promising.
I plugged back into my PC USB, and ran Calibre.
Hooray!
Everything seems to be "normal" now, with no error messages.
I tried reading the books I had previously and all it lost was my reading progress.
Oh well, no biggie
Lets try adding a book to my device from my library..
OK, all seems good now.


Conclusion: The Kobo Extended new version, and not the one offered from within the Calibre menu is a good one.

Thanks!
MauriceH is offline   Reply With Quote
Old 11-26-2016, 02:18 PM   #4
MauriceH
Junior Member
MauriceH began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2016
Device: Kobo Glo
It looked like that, but no, did not matter
Quote:
Originally Posted by DNSB View Post
That error message is a pretty good indication that your database is corrupted. The easiest way to fix it is to log out of your KA1 and then sign in to create a new database.

This will remove any annotations, etc. so you might want to grab a copy of the corrupted database before doing the sign out. Depending on how damaged the database is, you may be able to recover some information from it.

I had wondered about that, so, using Calibre I backed up my database to my PC, and then removed it from the device
No database, but similar errors.
So I put it back, and read more, then removed the old Kobo drivers and installed the new Extended Kobo driver.
That fixed it.
MauriceH is offline   Reply With Quote
Old 11-26-2016, 07:04 PM   #5
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 MauriceH View Post
I had wondered about that, so, using Calibre I backed up my database to my PC, and then removed it from the device
No database, but similar errors.
So I put it back, and read more, then removed the old Kobo drivers and installed the new Extended Kobo driver.
That fixed it.
Sorry, but it didn't. The KoboTouchExtended driver subclasses the KoboTouch driver. 95% of the function you get from the extended driver is actually in the KoboTouch driver. The errors you reported in your first post is in the common code, so would have happened if you had been running the extended driver at the beginning. Your other post tells me what happened.

As DNSB said, the database was corrupt. The solution to that is to sign out of the Kobo account and back in. This creates a new database. And gets you to do the setup again. If the database is to corrupt, the device delete the database and trigger the setup. According to your second post, this is what happened. The database was to corrupt, when you restarted the decice, the firmware couldn't use the database and you were prompted to do the setup. Then, all the books sideloaded to the device were processed into the new database. If you look, you will see that the reading status of all the books has been reset and any collections will be empty. Annotations might be there depending on other things.
davidfor is offline   Reply With Quote
Advert
Old 12-02-2016, 01:29 AM   #6
MauriceH
Junior Member
MauriceH began at the beginning.
 
Posts: 6
Karma: 10
Join Date: Mar 2016
Device: Kobo Glo
Informative exlanation
OK, that explanation makes sense, and explains a lot of things.

Thanks!

I guess I somewhat got lucky in that it ended up getting fixed, and not completely blown up.

My saga is, however, not quite over.
Today I downloaded a new EPUB, and started Calibre on my PC.

I went to add the book to my collection, and saw a long string of errors.
Unfortunately I did not capture that.
Afterwards, however, I see that the new book has been added, is in the master list, and is readable, at least on my PC.

Is there anything you could suggest I should now check?

Regards,
Maurice
MauriceH is offline   Reply With Quote
Old 12-02-2016, 05:23 AM   #7
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
Without the errors, I am mainly guessing. The things I would do are:

- Connect to calibre and see if it happens again.
- Remove the book that seemed to cause the problem and send it again.
- Use the Kobo Utilities plugin to check the database on the device. Or use an SQLite management application to do the same.
- Run calibre in debug mode and keep the log produced with the errors.

For me to debug remotely, the last one is the most useful.
davidfor is offline   Reply With Quote
Reply

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Updated to 4.3.4.4 and cc no longer connects to pc peaceridge Calibre Companion 3 02-14-2016 04:09 PM
Calibre Companion no longer connects BSewer Calibre Companion 3 07-03-2015 01:34 PM
Calibre Companion no longer connects BSewer Calibre Companion 6 06-15-2015 09:54 PM
Marvin No Longer Connects w/Calibre HisLittleOne Calibre 7 12-02-2014 10:21 PM
Calibre crashes and will no longer launch upon installing Marvin XD holymadness Marvin 11 09-13-2013 07:12 PM


All times are GMT -4. The time now is 03:33 AM.

Contact Us - FAQ - Guidelines - Privacy - Top

MobileRead.com is a privately owned, operated and funded community.