Thread: Kobo can't open database
View Single Post
Old 05-27-2017, 08:51 AM   #2
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 Dei View Post
Dear Goyal, I used calibre on Mac Apple for a lot of years with great satisfaction, connecting with Kobo Touch..
Yesterday I updated calibre to 2.85.1 version and, on the same time (unfortunately), I updated my Kobo Touch.
After that when I connect my Kobo Touch to calibre, appears a window the reads "It's impossible to connect with database" : after a lot of tests I discovered the trouble is the SD card, If I leave the card from Kobo, calibre "sees" the ebooks inside the device.
I tried to format the SD card but it's the same problem.
I don't think the issue is calibre, because on another MAC Apple with calibre 2.83 (the version I used before without problem) happens the same problem with the SD card.
On windows platform everything is normal and good.
What can I do ?
Sorry, that's my fault. I made a change to how the KoboTouch driver detected the drives from the device. Under some circumstances, they can be presented to calibre by the OS in such a way so that calibre and the driver sees the card as the main memory. Unfortunately my changed doesn't always work on a Mac. It is fine on a Windows machine as the method used was different.

I have a fix for this and have had a couple of OSX users test it it successfully. I will be checking this in shortly, and it should be included in the next beta build after that.

Also, the problem I was fixing was most likely to happen with the Touch. And I have had the most reports from Mac users. And the 4.4.x firmware included changes that seem to make it more likely to happen on the other OSes.
davidfor is offline   Reply With Quote