MobileRead Forums - View Single Post - [KOBO] Error communicating with device, CantOpenError: unable to open database file

LSH · 06-08-2020, 07:48 PM

Thanks very much for your quick and thorough response, davidfor.

The device is mounted and writeable on both Windows and Ubuntu.

I looked (and changed settings to show hidden files/folders) but could not see the directory ".kobo" or the file "KoboReader.sqlite".

I reinstalled the Kobo software and reset the device again. On the desktop software, I got as far as the window that says "Please plug in your eReader" on the desktop software. I reset the reader's clock, plugged it in, and told it I wanted to make changes to the library (instead of just recharge). When I did this, the file directory for the reader popped up on the computer screen. It's empty. The desktop software has not responded or given me any further instructions; it still says "Please plug in your eReader." The reader says it is connected and charging.

Without any previous ebook reader experience, it's hard to know whether this is expected behavior or not, or what to try next.

06-08-2020, 07:48 PM	#3
LSH Junior Member Posts: 6 Karma: 10 Join Date: Jun 2020 Device: Kobo eReader Wifi (original)	Thanks very much for your quick and thorough response, davidfor. The device is mounted and writeable on both Windows and Ubuntu. I looked (and changed settings to show hidden files/folders) but could not see the directory ".kobo" or the file "KoboReader.sqlite". I reinstalled the Kobo software and reset the device again. On the desktop software, I got as far as the window that says "Please plug in your eReader" on the desktop software. I reset the reader's clock, plugged it in, and told it I wanted to make changes to the library (instead of just recharge). When I did this, the file directory for the reader popped up on the computer screen. It's empty. The desktop software has not responded or given me any further instructions; it still says "Please plug in your eReader." The reader says it is connected and charging. Without any previous ebook reader experience, it's hard to know whether this is expected behavior or not, or what to try next.