Thread: Firmware 4.20.14622 has been released
View Single Post
Old 03-29-2020, 11:12 PM   #60
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 cine1952 View Post
Hi

I have an Aura One. I have about 400 books on it. Books that I have read (about 375) are classified in 3 categories (called "collections" in French):
read -: for those I did not like (or did not finish)
read +: for those I liked very much
read : for other books

I also have a category for books I am currently reading.

Each time I connect the Kobo to calibre (4.13), Kobo Utilities v2.11.0 makes a backup of the Kobo database.

I recently (manually) updated the Aura One from v4.19.14123 TO v4.20.14622.
The result: I see only 2 of my previously defined categories and one of them shows no books (of course there were books in this category before the upgrade).

What I tried:
1) I reinstalled v4.19.14123. This did not solve the problem
2) I copy/pasted the 4 files contained in the database backup (created just before upgrading to v4.20.14622) to the .kobo folder of the Aura One. I rebooted the reader. This did not solve the problem.
Nothing has changed in the collections support in either the firmware or the calibre driver. There shouldnt be anything different.

The most common reason for this is when someone has changed between the built-in KoboTouch driver and the KoboTouchExtended driver and have not updated the configuration for the driver. The two drivers need to be configured separately. Otherwise, there have been some cases where the configuration of the driver is lost. This has happened mostly for the KoboTouchExtended driver, but, might have happened with the built-in driver with one of the changes in the last few months.

If the configuration of the driver you are using is what you expect, then I would need to see a debug log to see what is happening. You can run calibre in debug mode, connect the device and let the connection jobs run. Then close calibre and the debug log will be run. Post or PM the full contents of the log. If you post it, start a separate thread for it. From the debug log, I can generally work out what has happened.
davidfor is offline   Reply With Quote